public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Arno Tiemersma <arno.tiemersma@gmail.com>,
	devel@driverdev.osuosl.org, eric.rost@mybabylon.net,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	jake@lwn.net, antonysaraev@gmail.com
Subject: Re: [PATCH] staging: skein: Fix checkpatch warnings
Date: Mon, 12 Jan 2015 09:40:47 -0500	[thread overview]
Message-ID: <20150112144047.GY24989@titan.lakedaemon.net> (raw)
In-Reply-To: <20150112143347.GE7568@mwanda>

On Mon, Jan 12, 2015 at 05:33:47PM +0300, Dan Carpenter wrote:
> On Mon, Jan 12, 2015 at 09:14:18AM -0500, Jason Cooper wrote:
> > Arno,
> > 
> > On Sat, Jan 10, 2015 at 04:00:47PM +0100, Arno Tiemersma wrote:
> > > Remove do {} while (0) loops around single statements in
> > > skein/skein_block.c
> > > 
> > > Signed-off-by: Arno Tiemersma <arno.tiemersma@gmail.com>
> > > ---
> > >  drivers/staging/skein/skein_block.c | 16 ++++------------
> > >  1 file changed, 4 insertions(+), 12 deletions(-)
> > 
> > Is this a V2?  Several people have been submitting patches for this
> > checkpatch issue.  Please check the staging ML and deconflict with other
> > submitters.
> 
> Why would it be a v2?

I had asked one person to do a little extra work validating that
removing the do{}while's hadn't changed the resulting object code.
Unfortunately, I forgot who that was :(  Only because there have been so
many people submitting the exact same thing, though...

> It's really normal to get a wave of people sending the exact same patch.
> There was one time where 7 people deleted the same whitespace in
> panel.c.

I suspect this is a combination of a) checkpatch.pl getting a more
enhanced handling of do{}while's in macros, and b) more folks doing the
Eudiptula (sp?) challenge.

> Don't worry too much about conflicts.  It either applies when Greg reads
> it or it doesn't and he kicks off an email.  Not a big deal.

Agreed from a patch management side.  I was attempting to encourage the
new submitters to starting integrating the mailinglist into their
workflow.

thx,

Jason.

  reply	other threads:[~2015-01-12 14:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-10 15:00 [PATCH] staging: skein: Fix checkpatch warnings Arno Tiemersma
2015-01-12 14:14 ` Jason Cooper
2015-01-12 14:33   ` Dan Carpenter
2015-01-12 14:40     ` Jason Cooper [this message]
2015-01-17 23:09 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2014-12-25 18:01 arno.tiemersma
2014-12-25 18:06 ` 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=20150112144047.GY24989@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=antonysaraev@gmail.com \
    --cc=arno.tiemersma@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=eric.rost@mybabylon.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jake@lwn.net \
    --cc=linux-kernel@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