From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: Andy Whitcroft <apw@canonical.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: checkpatch: Adjust regular expressions in $logFunctions
Date: Tue, 09 May 2017 14:16:52 -0700 [thread overview]
Message-ID: <1494364612.4564.1.camel@perches.com> (raw)
In-Reply-To: <bc5feee3-77d5-1850-cab0-eb37f128eaae@users.sourceforge.net>
On Tue, 2017-05-09 at 23:01 +0200, SF Markus Elfring wrote:
> > Perl is odd enough already adding more non-capture groups
> > when the arguments are clearly specified is harder to read.
>
> How do you think about to reformat the affected alternations?
> Will it become appropriate to give each element a separate line there?
I have no interest in changing checkpatch for no value.
_maybe_, breaking up the file into separate tests in
multiple files _could_ be useful.
prev parent reply other threads:[~2017-05-09 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 19:00 [PATCH] checkpatch: Adjust regular expressions in $logFunctions SF Markus Elfring
2017-05-09 20:52 ` Joe Perches
2017-05-09 21:01 ` SF Markus Elfring
2017-05-09 21:16 ` Joe Perches [this message]
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=1494364612.4564.1.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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