From: Kees Cook <kees@kernel.org>
To: ndesaulniers@google.com, Kees Cook <keescook@chromium.org>
Cc: 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,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] MAINTAINERS: refresh LLVM support
Date: Fri, 17 Nov 2023 14:53:12 -0800 [thread overview]
Message-ID: <8243E862-CFC1-4658-B07E-9FB87E34E12B@kernel.org> (raw)
In-Reply-To: <20231117-maintainers-v1-1-85f2a7422ed9@google.com>
On November 17, 2023 11:24:02 AM PST, ndesaulniers@google.com wrote:
>I'll be taking a step back from kernel work
NAK ;)
>to focus on my growing
>family and helping Google figure out its libc story.
These are both big challenges, worthy of your attention. :)
>For CLANG/LLVM BUILD SUPPORT I'm bumping myself down from maintainer to
>reviewer, adding Bill and Justin, and removing Tom (Tom and I confirmed this
>via private email; thanks for the work done Tom, ++beers_owed).
Thanks Tom, and glad to have Bill and Justin stepping up!
>Wake me when you need me.
As the prophecy has foretold!
>Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
We'll just report all issues as LTS kernel bugs and use the MAINTAINERS entries from there. ;) We'll miss you, but you won't be far!
Good hunting,
-Kees
--
Kees Cook
next prev parent reply other threads:[~2023-11-17 22:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 19:24 ndesaulniers
2023-11-17 20:55 ` Nathan Chancellor
2023-11-17 22:53 ` Kees Cook [this message]
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
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=8243E862-CFC1-4658-B07E-9FB87E34E12B@kernel.org \
--to=kees@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®