From: Yann Droneaud <ydroneaud@opteya.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Nicholas Krause <xerofoify@gmail.com>,
Adrian Remonda <adrianremonda@gmail.com>,
Murilo Opsfelder Araujo <mopsfelder@gmail.com>,
devel@driverdev.osuosl.org, waydi1@gmail.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
daniel@ffwll.ch, maarten.lankhorst@canonical.com,
sumit.semwal@linaro.org, Yann Droneaud <ydroneaud@opteya.com>
Subject: Re: [PATCH] Staging: android: sw_sync.c: fix missing blank line after declaration
Date: Thu, 31 Jul 2014 15:44:20 +0200 [thread overview]
Message-ID: <1406814260.23396.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20140731133059.GO4856@mwanda>
Hi,
Le jeudi 31 juillet 2014 à 16:30 +0300, Dan Carpenter a écrit :
> On Thu, Jul 31, 2014 at 03:00:19PM +0200, Yann Droneaud wrote:
> > Le lundi 28 juillet 2014 à 19:38 -0300, Murilo Opsfelder Araujo a
> > écrit :
> > > Fix coding style issue.
> > >
> > > Signed-off-by: Murilo Opsfelder Araujo <mopsfelder@gmail.com>
> >
> > Is this some kind of game ?
> >
> > The *same* patch was sent three times from three different email
> > addresses:
>
> This is just normal.
>
> Once I saw 7 people send the same patch. I was almost the third person
> to send a fix last week. I had the patch prepared to send, but I
> happened to look at my inbox before sending.
>
As the initial patch was sent by someone who has some trouble with the
way things are done here [1], it raise some, probably false, alarms.
[1] "Help with flame wars"
http://lists.kernelnewbies.org/pipermail/kernelnewbies/2014-July/011394.html
Regards.
--
Yann Droneaud
OPTEYA
prev parent reply other threads:[~2014-07-31 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 22:38 [PATCH] Staging: android: sw_sync.c: fix missing blank line after declaration Murilo Opsfelder Araujo
2014-07-31 0:17 ` Greg KH
2014-07-31 11:44 ` Murilo Opsfelder Araujo
2014-07-31 13:00 ` Yann Droneaud
2014-07-31 13:30 ` Dan Carpenter
2014-07-31 13:44 ` Yann Droneaud [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=1406814260.23396.6.camel@localhost.localdomain \
--to=ydroneaud@opteya.com \
--cc=adrianremonda@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=mopsfelder@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=waydi1@gmail.com \
--cc=xerofoify@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.