Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <d4b42858366e50f92b133ceb6399e9f16a7cef88.camel@perches.com>
Subject: Re: [PATCH] MAINTAINERS: add CLANG/LLVM BUILD SUPPORT info
From:   Joe Perches <joe@perches.com>
To:     Nick Desaulniers <ndesaulniers@google.com>,
        akpm@linux-foundation.org
Cc:     clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org
Date:   Wed, 19 Jun 2019 11:27:42 -0700
In-Reply-To: <20190619181844.57696-1-ndesaulniers@google.com>
References: <20190619181844.57696-1-ndesaulniers@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
User-Agent: Evolution 3.30.5-0ubuntu0.18.10.1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, 2019-06-19 at 11:18 -0700, Nick Desaulniers wrote:
> Add keyword support so that our mailing list gets cc'ed for clang/llvm
> patches.

You'd also possibly get cc'd on patches that merely mention
clang or llvm like any change to clang-format.  It could be
many files that aren't interesting.

$ git grep -i -w -P --name-only '(?i:clang|llvm)' | wc -l
134

> diff --git 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
> +W: https://clangbuiltlinux.github.io/
> +B: https://github.com/ClangBuiltLinux/linux/issues
> +C: irc://chat.freenode.net/clangbuiltlinux
> +S: Supported
> +K: \b(?i:clang|llvm)\b
> +

Please use a single tab after each : like below

CLANG/LLVM BUILD SUPPORT
L:	clang-built-linux@googlegroups.com
W:	https://clangbuiltlinux.github.io/
B:	https://github.com/ClangBuiltLinux/linux/issues
C:	irc://chat.freenode.net/clangbuiltlinux
S:	Supported
K:	\b(?i:clang|llvm)\b