From: Joe Perches <joe@perches.com>
To: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
Cc: apw@canonical.com, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] checkpatch: suggest using eth_zero_addr() and eth_broadcast_addr()
Date: Tue, 21 Apr 2015 15:27:27 -0700 [thread overview]
Message-ID: <1429655247.31675.20.camel@perches.com> (raw)
In-Reply-To: <5536C4C2.4000001@gmail.com>
On Tue, 2015-04-21 at 23:44 +0200, Mateusz Kulikowski wrote:
> On 21.04.2015 23:22, Joe Perches wrote:
> > On Tue, 2015-04-21 at 22:57 +0200, Mateusz Kulikowski wrote:
> (...)
> >>
> >> Perhaps it would be smarter to use (for both patches) $stat instead.
> >> This applies also to existing checks (like PREFER_ETHER_ADDR_COPY)
> >> so we can catch calls formatted like
> >>
> >> memset(very.long.structure->something.something_different42,
> >> 0xFF, ETH_ALEN);
> >
> > Yes, likely that's true.
> >
> > checkpatch couldn't --fix it easily unless it's on a
> > single line though.
>
> True, True; If you prefer $line and ability to --fix - I'll use that in v3
I suppose you could do both $line and $stat
and the fix would only work when it's on a
single line.
Perhaps something like this would work:
if ($line =~ /whatever/ ||
(defined($stat) && $stat =~ /whatever/)) {
if (WARN(...) &&
$fix) {
fixed[$fixlinenr] =~ s/whatever/appropriate/;
}
}
No worries about getting 'round the the list.
It'll get got eventually.
next prev parent reply other threads:[~2015-04-21 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 22:16 [PATCH v2 0/2] checkpatch: new ethernet address manipulation checks Mateusz Kulikowski
2015-04-19 22:16 ` [PATCH v2 1/2] checkpatch: suggest using ether_addr_equal*() Mateusz Kulikowski
2015-04-19 22:16 ` [PATCH v2 2/2] checkpatch: suggest using eth_zero_addr() and eth_broadcast_addr() Mateusz Kulikowski
2015-04-20 1:13 ` Joe Perches
2015-04-21 20:57 ` Mateusz Kulikowski
2015-04-21 21:22 ` Joe Perches
2015-04-21 21:44 ` Mateusz Kulikowski
2015-04-21 22:27 ` Joe Perches [this message]
2015-04-23 19:53 ` Mateusz Kulikowski
2015-04-23 23:54 ` Joe Perches
2015-04-23 23:55 ` Joe Perches
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=1429655247.31675.20.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mateusz.kulikowski@gmail.com \
--cc=netdev@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