[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6bb0ac7f70a12a4bb9cb6238b4e50e23674bde43.camel@perches.com>
Date: Wed, 19 Jun 2019 11:10:46 -0700
From: Joe Perches <joe@...ches.com>
To: Nick Desaulniers <ndesaulniers@...gle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Matthias Kaehlcke <mka@...omium.org>,
"David S . Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Alexander Duyck <alexander.h.duyck@...hat.com>,
netdev@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Douglas Anderson <dianders@...omium.org>,
Nathan Huckleberry <nhuck@...gle.com>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Nathan Chancellor <natechancellor@...il.com>
Subject: Re: [PATCH] net/ipv4: fib_trie: Avoid cryptic ternary expressions
On Wed, 2019-06-19 at 10:41 -0700, Nick Desaulniers wrote:
> On Wed, Jun 19, 2019 at 2:36 AM Joe Perches <joe@...ches.com> wrote:
> > On Tue, 2019-06-18 at 16:23 -0700, Nick Desaulniers wrote:
> > > As a side note, I'm going to try to see if MAINTAINERS and
> > > scripts/get_maintainers.pl supports regexes on the commit messages in
> > > order to cc our mailing list
> >
> > Neither. Why should either?
>
> Looks like `K:` is exactly what I'm looking for.
Using K: for commit message content isn't the intended
use, but if it works for you, fine by me.
> Joe, how does:
> https://github.com/ClangBuiltLinux/linux/commit/a0a64b8d65c4e7e033f49e48cc610d6e4002927e
> look?
You might consider using
K: \b(?i:clang|llvm)\b
to get case insensitive matches.
> Is there a maintainer for MAINTAINERS or do I just send the
> patch to Linus?
Generally MAINTAINER patches go via Andrew Morton or
indirectly along with other changes via a pull request
to Linus.
Powered by blists - more mailing lists