From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jason Cooper <jason@lakedaemon.net>
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 17:33:47 +0300 [thread overview]
Message-ID: <20150112143347.GE7568@mwanda> (raw)
In-Reply-To: <20150112141418.GW24989@titan.lakedaemon.net>
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?
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.
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.
regards,
dan carpenter
next prev parent reply other threads:[~2015-01-12 14:34 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 [this message]
2015-01-12 14:40 ` Jason Cooper
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=20150112143347.GE7568@mwanda \
--to=dan.carpenter@oracle.com \
--cc=antonysaraev@gmail.com \
--cc=arno.tiemersma@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric.rost@mybabylon.net \
--cc=gregkh@linuxfoundation.org \
--cc=jake@lwn.net \
--cc=jason@lakedaemon.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