From: Dan Carpenter <dan.carpenter@oracle.com>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
"Emil Goode" <emilgoode@gmail.com>,
"Shawn Guo" <shawn.guo@freescale.com>,
"Sascha Hauer" <kernel@pengutronix.de>,
"Russell King" <linux@arm.linux.org.uk>,
"Olof Johansson" <olof@lixom.net>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH] driver core/platform: remove unused implicit padding in platform_object
Date: Sat, 31 May 2014 15:05:27 +0300 [thread overview]
Message-ID: <20140531120526.GL15585@mwanda> (raw)
In-Reply-To: <1401523299.15490.6.camel@localhost.localdomain>
On Sat, May 31, 2014 at 10:01:39AM +0200, Yann Droneaud wrote:
> Hi Dan,
>
> Le vendredi 30 mai 2014 à 23:10 +0300, Dan Carpenter a écrit :
> > This changelog doesn't match the patch.
> >
>
> Hum, let me guess .... I've failed to set the proper subject prefix
> to add v6 suffic to PATCH:
> I've changed the patch title since v5 (from Emil Goode)... so it's like
> a new one.
>
> Is it really necessary to resend the patch ?
Oh. Sorry, I didn't understand what you were trying to say... You're
right.
For some reason I just looked at the patch first and then I started
reading the changelog and got to the bit about GCC on ARM and said
thought have been describing a different change without reading the
rest. This was my bad. I should have read more carefully.
Very thourough patch description. :)
regards,
dan carpenter
next prev parent reply other threads:[~2014-05-31 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 20:02 [PATCH] driver core/platform: remove unused implicit padding in platform_object Yann Droneaud
2014-05-30 20:10 ` Dan Carpenter
2014-05-31 8:01 ` Yann Droneaud
2014-05-31 12:05 ` Dan Carpenter [this message]
2014-06-01 8:00 ` Yann Droneaud
2014-06-01 17:47 ` Greg Kroah-Hartman
2014-06-02 8:36 ` Dan Carpenter
2014-06-01 10:19 ` Uwe Kleine-König
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=20140531120526.GL15585@mwanda \
--to=dan.carpenter@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=emilgoode@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=shawn.guo@freescale.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=ydroneaud@opteya.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox