public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Thu, 23 Apr 2015 16:55:18 -0700	[thread overview]
Message-ID: <1429833318.32612.47.camel@perches.com> (raw)
In-Reply-To: <1429833248.32612.46.camel@perches.com>

On Thu, 2015-04-23 at 16:54 -0700, Joe Perches wrote:
> On Thu, 2015-04-23 at 21:53 +0200, Mateusz Kulikowski wrote:
> > I noticed funny behavior about $stat matches - 
> > it reports the same error several times (including as "scope" whole file)
> > Is it feature or "feature" or I missed something?
> 
> You have to make sure the first character of $stat is a +
> 
> 	if ($stat =~ /\+(?:.*)\bmem<foo>

Make that

	if ($stat =~ /^\+(?:.*)\bmem<foo>



      reply	other threads:[~2015-04-23 23:55 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
2015-04-23 19:53             ` Mateusz Kulikowski
2015-04-23 23:54               ` Joe Perches
2015-04-23 23:55                 ` 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=1429833318.32612.47.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