public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, roel <12o3l@tiscali.nl>,
	lkml <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@xenotime.net>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] spin_lock_unlocked cleanups
Date: Fri, 28 Sep 2007 02:05:59 -0700	[thread overview]
Message-ID: <20070928020559.6b05f330.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070928085347.GB12086@shadowen.org>

On Fri, 28 Sep 2007 09:53:47 +0100 Andy Whitcroft <apw@shadowen.org> wrote:

> On Fri, Sep 28, 2007 at 01:26:56AM -0700, Andrew Morton wrote:
> > On Fri, 28 Sep 2007 10:17:30 +0200 Thomas Gleixner <tglx@linutronix.de> wrote:
> > 
> > > can we please add this to checkpatch.pl ? 
> > > 
> > > > -spinlock_t bpci_lock = SPIN_LOCK_UNLOCKED;
> > > > +DEFINE_SPINLOCK(bpci_lock);
> > 
> > That check is already in checkpatch.  Problem is that hardly anyone
> > runs the thing.
> > 
> > I think we're ready to wire checkpatch up to a email robot which monitors
> > the mailing lists and sends people nastygrams.  I bet that'll be popular ;)
> 
> That shouldn't be too hard.  checkpatch has been subscribed since birth
> but short circuiting the replies to me only.
> 
> I guess the main question is whether to reply-all or reply just to the
> sender when commenting on patches.  Perhaps for the sanity of the rest
> of the world, just the sender makes most sense.

For sure.

> > (I'd love it if it could detect wordwrapped and tab-expanded patches, too. 
> > You wouldn't _believe_...)
> 
> It should pick up both of these, the word-wrapping is already there as
> we detect lines within patch segments which don't start '[ +-]', the
> tab-expanded should be picked up as every line would be "don't use
> spaces use tabs for indent".

OK.

Often patches are wordwrapped only in the header:

--- old/drivers/ata/libata-sff.c	2007-04-26 12:02:46.000000000 -0400
+++ linux/drivers/ata/libata-sff.c	2007-04-29 08:29:27.000000000 -0400
@@ -413,6 +413,24 @@
 	ap->ops->irq_on(ap);

comes through as

--- old/drivers/ata/libata-sff.c	2007-04-26
12:02:46.000000000 -0400
+++ linux/drivers/ata/libata-sff.c	2007-04-29
08:29:27.000000000 -0400
@@ -413,6 +413,24 @@
 	ap->ops->irq_on(ap);

and the rest of the patch is good.

<tests it>

Yup, fooled you ;)

  reply	other threads:[~2007-09-28  9:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 21:36 [PATCH] spin_lock_unlocked cleanups roel
2007-09-28  8:17 ` Thomas Gleixner
2007-09-28  8:26   ` Andrew Morton
2007-09-28  8:30     ` Ingo Molnar
2007-09-28  8:55       ` Andrew Morton
2007-09-28  8:32     ` Thomas Gleixner
2007-09-28  8:56       ` Andy Whitcroft
2007-09-28  9:06         ` Thomas Gleixner
2007-09-28 21:15           ` Sean
2007-09-28  8:53     ` Andy Whitcroft
2007-09-28  9:05       ` Andrew Morton [this message]
2007-09-28 17:31     ` Mark Gross

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=20070928020559.6b05f330.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=12o3l@tiscali.nl \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    --cc=tglx@linutronix.de \
    /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