From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Versatile Express DT support
Date: Fri, 24 Feb 2012 10:04:50 +0000 [thread overview]
Message-ID: <1330077890.2727.14.camel@hornet.cambridge.arm.com> (raw)
In-Reply-To: <20120223225924.GA12404@mudshark.cambridge.arm.com>
Morning
On Thu, 2012-02-23 at 22:59 +0000, Will Deacon wrote:
> > ARM: vexpress: Use FDT data in platform SMP calls
>
> This patch has a curious commit message, which ends like:
>
> Signed-off-by: Pawel Moll <pawel.moll@arm.com>
>
> SMP update (change commit log!)
>
> Is that last line supposed to be there?
No, of course not - patch squashing leftover. Fixed now.
Thanks for both you and Tixy (who was actually faster ;-) for spotting
that!
Pawe?
next prev parent reply other threads:[~2012-02-24 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 18:00 [GIT PULL] Versatile Express DT support Pawel Moll
2012-02-23 22:59 ` Will Deacon
2012-02-24 10:04 ` Pawel Moll [this message]
2012-02-24 14:56 ` Arnd Bergmann
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=1330077890.2727.14.camel@hornet.cambridge.arm.com \
--to=pawel.moll@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).