public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	rdunlap@xenotime.net, jschopp@austin.ibm.com
Subject: Re: [PATCH] Check patch reports multiple var with a function assignment
Date: Tue, 31 Jul 2007 13:46:08 +0100	[thread overview]
Message-ID: <46AF2F10.40001@shadowen.org> (raw)
In-Reply-To: <46AEA245.9090300@windriver.com>

Jason Wessel wrote:
> Running checkpatch.pl products an warning when it should not.  I believe
> it can be fixed by adding to the regular expression, but feel free to
> fix it another way as I may not know all the cases this is trying to catch.

Thanks for the patch.  We had already caught this one and the test
itself now is likely to be shelved, a new release with this update in is
iminent.

-apw

      reply	other threads:[~2007-07-31 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31  2:45 [PATCH] Check patch reports multiple var with a function assignment Jason Wessel
2007-07-31 12:46 ` Andy Whitcroft [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=46AF2F10.40001@shadowen.org \
    --to=apw@shadowen.org \
    --cc=jason.wessel@windriver.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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