From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: changes for next
Date: Mon, 12 Sep 2011 11:03:49 +0200 [thread overview]
Message-ID: <4E6DCAF5.50607@atmel.com> (raw)
In-Reply-To: <201109102306.58340.arnd@arndb.de>
Le 10/09/2011 23:06, Arnd Bergmann :
> On Friday 09 September 2011, Nicolas Ferre wrote:
>> Can you please pull the following changes since commit ddf28352b80c86754a6424e3a61e8bdf9213b3c7:
>>
>> Linux 3.1-rc5 (2011-09-04 15:45:10 -0700)
>>
>> They are available in the git repository at:
>> git://github.com/at91linux/linux-at91.git at91-next
>>
>> They have been present on linux-arm-kernel for some time and where recently added in linux-next.
>> Stephen resolved some trivial conflicts relatives to the removal of a board file (Cf:
>> https://lkml.org/lkml/2011/9/9/96 ).
>>
>> A series by Thomas is touching the USB subsystem: ohci-at91.c but as most of changes are in the at91 directory, it makes more sense to take them in arm-soc.
>
> Hi Nicolas,
>
> I've resumed pulling patches and uploaded them to git.linaro.org while
> master.kernel.org continues to be unavailable.
>
> I've decided to split your branch into two separate branches 'board'
> and 'devel' to better match the code from other soc trees in a way
> that I can send forward to Linus. Please check that the split trees
> actually make sense, and tell me if that's ok for you or if you would
> prefer them split differently.
I have checked and It is perfect for me.
Thanks a lot Arnd, bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Josef Holzmayr <holzmayr@rsi-elektrotechnik.de>,
Nico Erfurth <ne@erfurth.eu>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Andrew Victor <linux@maxim.org.za>
Subject: Re: [GIT PULL] at91: changes for next
Date: Mon, 12 Sep 2011 11:03:49 +0200 [thread overview]
Message-ID: <4E6DCAF5.50607@atmel.com> (raw)
In-Reply-To: <201109102306.58340.arnd@arndb.de>
Le 10/09/2011 23:06, Arnd Bergmann :
> On Friday 09 September 2011, Nicolas Ferre wrote:
>> Can you please pull the following changes since commit ddf28352b80c86754a6424e3a61e8bdf9213b3c7:
>>
>> Linux 3.1-rc5 (2011-09-04 15:45:10 -0700)
>>
>> They are available in the git repository at:
>> git://github.com/at91linux/linux-at91.git at91-next
>>
>> They have been present on linux-arm-kernel for some time and where recently added in linux-next.
>> Stephen resolved some trivial conflicts relatives to the removal of a board file (Cf:
>> https://lkml.org/lkml/2011/9/9/96 ).
>>
>> A series by Thomas is touching the USB subsystem: ohci-at91.c but as most of changes are in the at91 directory, it makes more sense to take them in arm-soc.
>
> Hi Nicolas,
>
> I've resumed pulling patches and uploaded them to git.linaro.org while
> master.kernel.org continues to be unavailable.
>
> I've decided to split your branch into two separate branches 'board'
> and 'devel' to better match the code from other soc trees in a way
> that I can send forward to Linus. Please check that the split trees
> actually make sense, and tell me if that's ok for you or if you would
> prefer them split differently.
I have checked and It is perfect for me.
Thanks a lot Arnd, bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2011-09-12 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 12:42 [GIT PULL] at91: changes for next Nicolas Ferre
2011-09-09 12:42 ` Nicolas Ferre
2011-09-10 21:06 ` Arnd Bergmann
2011-09-10 21:06 ` Arnd Bergmann
2011-09-12 9:03 ` Nicolas Ferre [this message]
2011-09-12 9:03 ` 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=4E6DCAF5.50607@atmel.com \
--to=nicolas.ferre@atmel.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 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.