From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: fixes for 3.1
Date: Fri, 26 Aug 2011 17:52:58 +0200 [thread overview]
Message-ID: <201108261752.58929.arnd@arndb.de> (raw)
In-Reply-To: <4E54CE15.1020504@atmel.com>
On Wednesday 24 August 2011, Nicolas Ferre wrote:
> Hi Arnd,
>
> Can you please pull this "fixes" patch since commit fcb8ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c:
>
> Linux 3.1-rc3 (2011-08-22 11:42:53 -0700)
>
> It is available in the git repository at:
> git://github.com/at91linux/linux-2.6-at91.git at91-fixes
>
> Jean-Christophe PLAGNIOL-VILLARD (1):
> at91: at91sam9261.c: fix typo in t2_clk alias for atmel_tcb.0
>
> arch/arm/mach-at91/at91sam9261.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> It is a single patch but I prefer to send you a
> pull request as it may integrate better with your
> flow...
Yes that helps. I pulled it into the fixes branch now, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: "Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Remy Bohmer <linux@bohmer.net>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] at91: fixes for 3.1
Date: Fri, 26 Aug 2011 17:52:58 +0200 [thread overview]
Message-ID: <201108261752.58929.arnd@arndb.de> (raw)
In-Reply-To: <4E54CE15.1020504@atmel.com>
On Wednesday 24 August 2011, Nicolas Ferre wrote:
> Hi Arnd,
>
> Can you please pull this "fixes" patch since commit fcb8ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c:
>
> Linux 3.1-rc3 (2011-08-22 11:42:53 -0700)
>
> It is available in the git repository at:
> git://github.com/at91linux/linux-2.6-at91.git at91-fixes
>
> Jean-Christophe PLAGNIOL-VILLARD (1):
> at91: at91sam9261.c: fix typo in t2_clk alias for atmel_tcb.0
>
> arch/arm/mach-at91/at91sam9261.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> It is a single patch but I prefer to send you a
> pull request as it may integrate better with your
> flow...
Yes that helps. I pulled it into the fixes branch now, thanks!
Arnd
next prev parent reply other threads:[~2011-08-26 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 10:10 [GIT PULL] at91: fixes for 3.1 Nicolas Ferre
2011-08-24 10:10 ` Nicolas Ferre
2011-08-26 15:52 ` Arnd Bergmann [this message]
2011-08-26 15:52 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2011-09-28 21:19 [GIT PULL] at91 " Nicolas FERRE
2011-09-28 21:19 ` Nicolas FERRE
2011-09-30 20:17 ` Arnd Bergmann
2011-09-30 20:17 ` Arnd Bergmann
2011-10-03 8:09 ` Nicolas Ferre
2011-10-03 8:09 ` Nicolas Ferre
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=201108261752.58929.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.