From: Nathan Chancellor <nathan@kernel.org>
To: ndesaulniers@google.com
Cc: Kees Cook <keescook@chromium.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: Fri, 17 Nov 2023 13:55:43 -0700 [thread overview]
Message-ID: <20231117205543.GA3619211@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20231117-maintainers-v1-1-85f2a7422ed9@google.com>
On Fri, Nov 17, 2023 at 11:24:02AM -0800, 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.
>
> As such, remove myself from reviewer for:
> - CLANG CONTROL FLOW INTEGRITY SUPPORT
> - COMPILER ATTRIBUTES
> - KERNEL BUILD
>
> 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).
>
> It has been my pleasure to work with everyone to improve the toolchain
> portability of the Linux kernel, and to help bring LLVM to the table as a
> competitor. The work here is not done. I have a few last LLVM patches in the
> works to improve stack usage of clang which has been our longest standing open
> issue (getting "rm" inline asm constraints to DTRT is part of that). But
> looking back I'm incredibly proud of where we are to today relative to where we
> were when we started the ClangBuiltLinux journey, and am confident that the
> team and processes we have put in place will continue to be successful. I
> continue to believe that a rising tide will lift all boats.
>
> 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.
>
> Wake me when you need me.
>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Definitely bittersweet but I wish you nothing but the best on the other
side of the fence :)
Acked-by: Nathan Chancellor <nathan@kernel.org>
> ---
> MAINTAINERS | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 482d428472e7..1e6692697167 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5076,7 +5076,6 @@ CLANG CONTROL FLOW INTEGRITY SUPPORT
> M: Sami Tolvanen <samitolvanen@google.com>
> M: Kees Cook <keescook@chromium.org>
> R: Nathan Chancellor <nathan@kernel.org>
> -R: Nick Desaulniers <ndesaulniers@google.com>
> L: llvm@lists.linux.dev
> S: Supported
> B: https://github.com/ClangBuiltLinux/linux/issues
> @@ -5091,8 +5090,9 @@ F: .clang-format
>
> CLANG/LLVM BUILD SUPPORT
> M: Nathan Chancellor <nathan@kernel.org>
> -M: Nick Desaulniers <ndesaulniers@google.com>
> -R: Tom Rix <trix@redhat.com>
> +R: Nick Desaulniers <ndesaulniers@google.com>
> +R: Bill Wendling <morbo@google.com>
> +R: Justin Stitt <justinstitt@google.com>
> L: llvm@lists.linux.dev
> S: Supported
> W: https://clangbuiltlinux.github.io/
> @@ -5242,7 +5242,6 @@ F: drivers/platform/x86/compal-laptop.c
>
> COMPILER ATTRIBUTES
> M: Miguel Ojeda <ojeda@kernel.org>
> -R: Nick Desaulniers <ndesaulniers@google.com>
> S: Maintained
> F: include/linux/compiler_attributes.h
>
> @@ -11516,7 +11515,6 @@ F: fs/autofs/
> KERNEL BUILD + files below scripts/ (unless maintained elsewhere)
> M: Masahiro Yamada <masahiroy@kernel.org>
> R: Nathan Chancellor <nathan@kernel.org>
> -R: Nick Desaulniers <ndesaulniers@google.com>
> R: Nicolas Schier <nicolas@fjasle.eu>
> L: linux-kbuild@vger.kernel.org
> S: Maintained
>
> ---
> base-commit: 6bc40e44f1ddef16a787f3501b97f1fff909177c
> change-id: 20231117-maintainers-88eac4c024a1
>
> Best regards,
> --
> Nick Desaulniers <ndesaulniers@google.com>
>
>
next prev parent reply other threads:[~2023-11-17 20:55 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 [this message]
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
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=20231117205543.GA3619211@dev-arch.thelio-3990X \
--to=nathan@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=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®