All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: ndesaulniers@google.com
Cc: Kees Cook <keescook@chromium.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>, Tom Rix <trix@redhat.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nicolas Schier <nicolas@fjasle.eu>,
	llvm@lists.linux.dev, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: refresh LLVM support
Date: Tue, 21 Nov 2023 11:58:17 +0100	[thread overview]
Message-ID: <CA+icZUXFGp-yoWUHhbowz6YJyoULCgtjSZ-fTpRg8YvVD9V5gg@mail.gmail.com> (raw)
In-Reply-To: <20231117-maintainers-v1-1-85f2a7422ed9@google.com>

On Fri, Nov 17, 2023 at 8:24 PM <ndesaulniers@google.com> wrote:
>
> As discussed at the ClangBuiltLinux '23 meetup (co-located with Linux Plumbers
> Conf '23), I'll be taking a step back from kernel work to focus on my growing
> family and helping Google figure out its libc story. So I think it's time to
> formally hand over the reigns to my co-maintainer Nathan.
>

Hi Nick,

WoW (C)lang(B)uilt(L)inux baby coming soon - your best patch well done!
(  "Catherine Beatrix Luana" might be a good first-name (my
Suggested-by when it's female) ).

> I identify first and foremost as a Linux kernel developer, and an LLVM dev
> second. May it be a cold day in hell when that changes.

Of course, I can understand these 3+ years of working on both sides -
Linux kernel and LLVM toolchain - might be very time-consuming and
hopefully with positive stress.
Best luck and more for the new challenges!
...and thanks Google jumped into it.

Thanks for inviting and participating in the First Meetup of
ClangBuiltLinux in Zurich - February 2020.
I see your slogan "Share Knowledge Aggressively" as a life motto :-).

Thanks and more.

Best regards,
-Sedat-

  parent reply	other threads:[~2023-11-21 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 19:24 [PATCH] MAINTAINERS: refresh LLVM support ndesaulniers
2023-11-17 20:55 ` Nathan Chancellor
2023-11-17 22:53 ` Kees Cook
2023-11-18 19:06   ` Bill Wendling
2023-11-19 17:17 ` Masahiro Yamada
2023-11-22  4:47   ` Kees Cook
2023-11-22  5:06     ` Masahiro Yamada
2023-11-20 19:46 ` Justin Stitt
2023-11-20 20:14 ` Miguel Ojeda
2023-11-20 20:22 ` Bill Wendling
2023-11-21 10:58 ` Sedat Dilek [this message]
2023-11-21 21:30   ` Bill Wendling
2023-11-28  0:34 ` Kees Cook
2023-12-01  8:04   ` Sedat Dilek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+icZUXFGp-yoWUHhbowz6YJyoULCgtjSZ-fTpRg8YvVD9V5gg@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=justinstitt@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=ojeda@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=trix@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.