From: Louis Taylor <louis@kragniz.eu>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: akpm@linux-foundation.org, clang-built-linux@googlegroups.com,
joe@perches.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add CLANG/LLVM BUILD SUPPORT info
Date: Wed, 19 Jun 2019 20:16:05 +0100 [thread overview]
Message-ID: <20190619191605.GA5837@gmail.com> (raw)
In-Reply-To: <20190619181844.57696-1-ndesaulniers@google.com>
On Wed, Jun 19, 2019 at 11:18:44AM -0700, 'Nick Desaulniers' via Clang Built Linux wrote:
> Add keyword support so that our mailing list gets cc'ed for clang/llvm
> patches. We're pretty active on our mailing list so far as code review.
> There are numerous Googlers like myself that are paid to support
> building the Linux kernel with Clang and LLVM.
>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
> ---
> Thanks for Joe Perches for help on the syntax for the case insensitive
> syntax.
>
> MAINTAINERS | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ef58d9a881ee..fa798cc48e34 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3940,6 +3940,14 @@ M: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
> S: Maintained
> F: .clang-format
>
> +CLANG/LLVM BUILD SUPPORT
> +L: clang-built-linux@googlegroups.com
I think this should have "(moderated for non-subscribers)" added.
Cheers,
Louis
next prev parent reply other threads:[~2019-06-19 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 18:18 Nick Desaulniers
2019-06-19 18:27 ` Joe Perches
2019-06-19 19:53 ` Nick Desaulniers
2019-06-20 0:19 ` [PATCH v2] " Nick Desaulniers
2019-06-20 2:54 ` Nathan Chancellor
2019-06-19 19:16 ` Louis Taylor [this message]
2019-06-19 19:50 ` [PATCH] " Nick Desaulniers
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=20190619191605.GA5837@gmail.com \
--to=louis@kragniz.eu \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®