From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: "'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] at91 fixes for 3.2-rc4
Date: Tue, 6 Dec 2011 14:16:01 +0000 [thread overview]
Message-ID: <201112061416.01718.arnd@arndb.de> (raw)
In-Reply-To: <4ED65F6D.4020402@atmel.com>
On Wednesday 30 November 2011, Nicolas Ferre wrote:
> Here are a few fixes for AT91. I have noted 3.2-rc4 in the subject but it
> is true that it can go in another -rc revision as I have seen your recent
> pull request to Linus...
>
> The following changes since commit caca6a03d365883564885f2c1da3e88dcf65d139:
Pulled into arm-soc/fixes now. Thanks!
Arnd
prev parent reply other threads:[~2011-12-06 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 16:53 [GIT PULL] at91 fixes for 3.2-rc4 Nicolas Ferre
2011-11-30 17:37 ` Arnd Bergmann
2011-12-06 14:16 ` Arnd Bergmann [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=201112061416.01718.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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