From: Joe Perches <joe@perches.com>
To: Nick Desaulniers <ndesaulniers@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matthias Kaehlcke <mka@chromium.org>,
"David S . Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Alexander Duyck <alexander.h.duyck@redhat.com>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Nathan Huckleberry <nhuck@google.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Nathan Chancellor <natechancellor@gmail.com>
Subject: Re: [PATCH] net/ipv4: fib_trie: Avoid cryptic ternary expressions
Date: Wed, 19 Jun 2019 11:10:46 -0700 [thread overview]
Message-ID: <6bb0ac7f70a12a4bb9cb6238b4e50e23674bde43.camel@perches.com> (raw)
In-Reply-To: <CAKwvOdkJCt7Du01e3LreLdpREPuZXWYnUad6WzqwO_o4i0yk7A@mail.gmail.com>
On Wed, 2019-06-19 at 10:41 -0700, Nick Desaulniers wrote:
> On Wed, Jun 19, 2019 at 2:36 AM Joe Perches <joe@perches.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.
next prev parent reply other threads:[~2019-06-19 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 21:14 Matthias Kaehlcke
2019-06-18 21:45 ` Doug Anderson
2019-06-18 22:57 ` Matthias Kaehlcke
2019-06-18 23:04 ` Nathan Chancellor
2019-06-18 23:21 ` Matthias Kaehlcke
2019-06-19 2:00 ` Alexander Duyck
2019-06-18 23:23 ` Nick Desaulniers
2019-06-19 9:36 ` Joe Perches
2019-06-19 17:41 ` Nick Desaulniers
2019-06-19 18:10 ` Joe Perches [this message]
2019-06-19 21:29 ` David Miller
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=6bb0ac7f70a12a4bb9cb6238b4e50e23674bde43.camel@perches.com \
--to=joe@perches.com \
--cc=alexander.h.duyck@redhat.com \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=nhuck@google.com \
--cc=torvalds@linux-foundation.org \
--cc=yoshfuji@linux-ipv6.org \
/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®