MAINTAINERS: add CLANG/LLVM BUILD SUPPORT info
PATCH 1/1 MAINTAINERS: add CLANG/LLVM BUILD SUPPORT info
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.
---
Thanks for Joe Perches for help on the syntax for the case insensitive syntax.
MAINTAINERS | 8 ++++++++ 1 file changed, 8 insertions(+)
MAINTAINERS +8 -0
@@ -3940,6 +3940,14 @@ M: Miguel Ojeda <[email protected]> S: Maintained F: .clang-format +CLANG/LLVM BUILD SUPPORT +L: [email protected] +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 + CLEANCACHE API M: Konrad Rzeszutek Wilk <[email protected]> L: [email protected]
Signature · 1 line
2.22.0.410.gd8fdbe21b5-goog
Quoted 2 lines · Nick Desaulniers
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
MAINTAINERS
Quoted 1 line
MAINTAINERS +0
-0
[]
MAINTAINERS M: Miguel Ojeda <[email protected]> · line 3950
Quoted 12 lines
MAINTAINERS +8
-0@@ -3940,6 +3940,14 @@ M: Miguel Ojeda <[email protected]> S: Maintained F: .clang-format +CLANG/LLVM BUILD SUPPORT +L: [email protected] +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: [email protected]
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
Quoted 11 lines · Joe Perches
Quoted 2 lines · Nick Desaulniers
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
That's very much intentional. We currently get ~11 emails a day from various CI services (KernelCI, 0day bot), patch authors, etc. so I don't think this adds too much more and it's mostly signal (signal to noise). Maybe the bpf stuff would be less relevant, but I don't think it hurts.
Quoted 1 line
Please use a single tab after each : like below
gah! My editor does flag this
(https://github.com/nickdesaulniers/dotfiles/blob/37359525f5a403b4ed2d3f9d1bbbee2da8ec8115/.vimrc#L35-L41)
whether or not I notice is sadly another story. Good catch, v2 inbound.
Signature · 2 lines
Thanks, ~Nick Desaulniers
PATCH v2 1/1 MAINTAINERS: add CLANG/LLVM BUILD SUPPORT info
In reply to Joe PerchesAdd 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.
---
Changes V1 -> V2:
- tabs vs spaces as per Joe Perches
MAINTAINERS | 8 ++++++++ 1 file changed, 8 insertions(+)
MAINTAINERS +8 -0
@@ -3940,6 +3940,14 @@ M: Miguel Ojeda <[email protected]> S: Maintained F: .clang-format +CLANG/LLVM BUILD SUPPORT +L: [email protected] +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 + CLEANCACHE API M: Konrad Rzeszutek Wilk <[email protected]> L: [email protected]
Signature · 1 line
2.22.0.410.gd8fdbe21b5-goog
Quoted 6 lines · Nick Desaulniers' via Clang Built Linux
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 <[email protected]>
FWIW, if it is not too late:
Quoted 29 lines
---
Changes V1 -> V2:
- tabs vs spaces as per Joe PerchesMAINTAINERS | 8 ++++++++ 1 file changed, 8 insertions(+)MAINTAINERS +8
-0@@ -3940,6 +3940,14 @@ M: Miguel Ojeda <[email protected]> S: Maintained F: .clang-format +CLANG/LLVM BUILD SUPPORT +L: [email protected] +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 + CLEANCACHE API M: Konrad Rzeszutek Wilk <[email protected]> L: [email protected]Signature · 1 line
2.22.0.410.gd8fdbe21b5-goog
Quoted 18 lines · Nick Desaulniers' via Clang Built Linux
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 <[email protected]>---
Thanks for Joe Perches for help on the syntax for the case insensitive syntax.MAINTAINERS | 8 ++++++++ 1 file changed, 8 insertions(+)MAINTAINERS +0
-0
MAINTAINERS M: Miguel Ojeda <[email protected]> · line 3944
Quoted 5 lines
MAINTAINERS +2
-0@@ -3940,6 +3940,14 @@ M: Miguel Ojeda <[email protected]> S: Maintained F: .clang-format +CLANG/LLVM BUILD SUPPORT +L: [email protected]
I think this should have "(moderated for non-subscribers)" added.
Cheers,
Louis
Quoted 10 lines · Louis Taylor
MAINTAINERS M: Miguel Ojeda <[email protected]> · line 3944
Quoted 6 lines · Nick Desaulniers' via Clang Built Linux
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.
MAINTAINERS +2
-0+CLANG/LLVM BUILD SUPPORT +L: [email protected]I think this should have "(moderated for non-subscribers)" added.
The current setting is "anyone from the web [may post]" as otherwise the various CI services reporting there have issues. There is a basic spam filter that emails me every so often. Not sure if that's quite considered "moderated for non-subscribers" or if I'm just being overly pedantic? (Point being that I don't think you have to subscribe to post)
Signature · 2 lines
Thanks, ~Nick Desaulniers