linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add LLVM maintainers
Date: Tue, 25 Aug 2020 07:45:25 -0700	[thread overview]
Message-ID: <20200825144525.GA128234@ubuntu-n2-xlarge-x86> (raw)
In-Reply-To: <20200825143540.2948637-1-ndesaulniers@google.com>

On Tue, Aug 25, 2020 at 07:35:40AM -0700, Nick Desaulniers wrote:
> Nominate Nathan and myself to be point of contact for clang/LLVM related
> support, after a poll at the LLVM BoF at Linux Plumbers Conf 2020.
> 
> While corporate sponsorship is beneficial, its important to not entrust
> the keys to the nukes with any one entity. Should Nathan and I find
> ourselves at the same employer, I would gladly step down.
> 
> Cc: clang-built-linux@googlegroups.com
> Cc: Nathan Chancellor <natechancellor@gmail.com>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>

Acked-by: Nathan Chancellor <natechancellor@gmail.com>

Thanks for sending the patch!

> ---
>  MAINTAINERS | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 33aab0c88118..0cbb24753153 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4249,6 +4249,8 @@ S:	Maintained
>  F:	.clang-format
>  
>  CLANG/LLVM BUILD SUPPORT
> +M:	Nathan Chancellor <natechancellor@gmail.com>
> +M:	Nick Desaulniers <ndesaulniers@google.com>
>  L:	clang-built-linux@googlegroups.com
>  S:	Supported
>  W:	https://clangbuiltlinux.github.io/
> -- 
> 2.28.0.297.g1956fa8f8d-goog
> 

  reply	other threads:[~2020-08-25 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 14:35 [PATCH] MAINTAINERS: add LLVM maintainers Nick Desaulniers
2020-08-25 14:45 ` Nathan Chancellor [this message]
2020-08-25 14:45 ` Sedat Dilek
2020-08-27  7:57 ` Miguel Ojeda
2020-08-27  9:43 ` Lukas Bulwahn

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=20200825144525.GA128234@ubuntu-n2-xlarge-x86 \
    --to=natechancellor@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.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;
as well as URLs for NNTP newsgroup(s).