All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@canonical.com>
To: Joe Perches <joe@perches.com>
Cc: Marco Stornelli <marco.stornelli@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RESEND] scripts: add no-warning option to the checkpatch script
Date: Tue, 21 Dec 2010 12:51:10 +0000	[thread overview]
Message-ID: <20101221125110.GI18715@shadowen.org> (raw)
In-Reply-To: <1292846770.22702.440.camel@Joe-Laptop>

On Mon, Dec 20, 2010 at 04:06:10AM -0800, Joe Perches wrote:
> On Mon, 2010-12-20 at 12:48 +0100, Marco Stornelli wrote:
> > 2010/12/20 Joe Perches <joe@perches.com>:
> > > On Mon, 2010-12-20 at 09:37 +0100, Marco Stornelli wrote:
> > >> 2010/12/20 Joe Perches <joe@perches.com>:
> > >> > Why do you think it's useful?
> > >> To "debug" a patch from style point of view, I think it's useful to
> > >> fix before the errors and then the warnings. So this option it's
> > >> useful as a "filter". However, I added you in cc: because of a reply
> > >> to my first patch that indicated you as a person interested in this
> > >> scope.
> > > Perhaps then it'd be better to filter/enable/disable
> > > the 3 current categories of messages.
> > > Maybe something like this:
> > Yeah, very good. Will it be inserted in mainline?
> 
> Dunno.  Maybe if Andy thinks it worthwhile.
> He takes his time about this sort of thing.

At a quick skim that seems a more comprehensive approach.  I've been lax
as always picking things up but with the quiet time coming I hope to
hoover up the left overs and push them out.

Thanks.

-apw

      reply	other threads:[~2010-12-21 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19  9:28 [PATCH][RESEND] scripts: add no-warning option to the checkpatch script Marco Stornelli
2010-12-20  2:52 ` Joe Perches
2010-12-20  8:37   ` Marco Stornelli
2010-12-20  9:22     ` Joe Perches
2010-12-20 11:48       ` Marco Stornelli
2010-12-20 12:06         ` Joe Perches
2010-12-21 12:51           ` 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=20101221125110.GI18715@shadowen.org \
    --to=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.stornelli@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.