From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, Andrew Victor <linux@maxim•org.za>,
Nicolas Ferre <nicolas.ferre@atmel•com>,
Russell King <rmk@arm•linux.org.uk>
Subject: Re: at91 next tree
Date: Sat, 23 Apr 2011 04:09:40 +0200 [thread overview]
Message-ID: <20110423020940.GC23775@game.jcrosoft.org> (raw)
In-Reply-To: <20110423095558.99ee7136.sfr@canb.auug.org.au>
On 09:55 Sat 23 Apr , Stephen Rothwell wrote:
> 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. It will be included in the next
> release (probably April 27) unless someone objects. I have cc'd the
> other listed maintainers and Russell just in case.
>
> I notice that there is currently nothing in that tree (relative to Linus'
> tree). This is not a problem for me, I mention it only in case something
> is wrong at your end.
Normal I just prepare it
we have a at91-l2 where we prepare the next end then we merge it at91-next
I'm preparing the next this week-end
>
> Currently I have listed only you (Jean-Christophe) as a contact in case I
> have problems with the tree - if there are others that should be listed
> as well, please let me know.
please put Nicolas too
Andrew do you want to be in Cc too?
Best Regards,
J.
next prev parent reply other threads:[~2011-04-23 2:18 UTC|newest]
Thread overview: 7+ 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 [this message]
2011-04-23 2:39 ` Stephen Rothwell
2011-04-23 16:06 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-09 12:14 ` Nicolas Ferre
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=20110423020940.GC23775@game.jcrosoft.org \
--to=plagnioj@jcrosoft$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@maxim$(echo .)org.za \
--cc=nicolas.ferre@atmel$(echo .)com \
--cc=rmk@arm$(echo .)linux.org.uk \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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