From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Andrew Victor <linux@maxim.org.za>,
Russell King <rmk@arm.linux.org.uk>,
Patrice VILCHEZ <patrice.vilchez@atmel.com>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: at91 next tree
Date: Fri, 09 Sep 2011 14:14:19 +0200 [thread overview]
Message-ID: <4E6A031B.6020804@atmel.com> (raw)
In-Reply-To: <20110423095558.99ee7136.sfr@canb.auug.org.au>
Stephen,
Le 23/04/2011 01:55, Stephen Rothwell :
> Hi,
>
> On Fri, 22 Apr 2011 17:51:22 +0200 Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> wrote:
>>
>> I'd like to known how we could get the at91 at91-next branch pull
>> in the next tree automaticaly?
>
> You request it :-)
>
>> git://github.com/at91linux/linux-2.6-at91.git at91-next
>
> I have added that tree to linux-next.
Can you please move our at91-next branch that is included currently in
linux-next to the "2.6-less" github tree?
git://github.com/at91linux/linux-at91.git
(I hope that the merge conflicts that you have just resolved will not
suffer from this move: but as commits are the same, I am pretty sure
that it will be transparent).
Thanks for your help, best regards,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: at91 next tree
Date: Fri, 09 Sep 2011 14:14:19 +0200 [thread overview]
Message-ID: <4E6A031B.6020804@atmel.com> (raw)
In-Reply-To: <20110423095558.99ee7136.sfr@canb.auug.org.au>
Stephen,
Le 23/04/2011 01:55, Stephen Rothwell :
> Hi,
>
> On Fri, 22 Apr 2011 17:51:22 +0200 Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> wrote:
>>
>> I'd like to known how we could get the at91 at91-next branch pull
>> in the next tree automaticaly?
>
> You request it :-)
>
>> git://github.com/at91linux/linux-2.6-at91.git at91-next
>
> I have added that tree to linux-next.
Can you please move our at91-next branch that is included currently in
linux-next to the "2.6-less" github tree?
git://github.com/at91linux/linux-at91.git
(I hope that the merge conflicts that you have just resolved will not
suffer from this move: but as commits are the same, I am pretty sure
that it will be transparent).
Thanks for your help, best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2011-09-09 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 15:51 at91 next tree Jean-Christophe PLAGNIOL-VILLARD
2011-04-22 23:55 ` Stephen Rothwell
2011-04-23 2:09 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-23 2:39 ` Stephen Rothwell
2011-04-23 16:06 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-09 12:14 ` Nicolas Ferre [this message]
2011-09-09 12:14 ` Nicolas Ferre
2011-09-11 4:10 ` Stephen Rothwell
2011-09-11 4:10 ` Stephen Rothwell
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=4E6A031B.6020804@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=patrice.vilchez@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=rmk@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
/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.