From: Rusty Russell <rusty@rustcorp.com.au>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Greg Ungerer <gerg@snapgear.com>, Jonas Bonn <jonas@southpole.se>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Ungerer <gerg@uclinux.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: linux-next: manual merge of the rr tree with the tree
Date: Thu, 21 Jul 2011 17:25:45 +0930 [thread overview]
Message-ID: <8739i02hku.fsf@rustcorp.com.au> (raw)
In-Reply-To: <4E256A2E.50607@cam.ac.uk>
On Tue, 19 Jul 2011 12:27:42 +0100, Jonathan Cameron <jic23@cam.ac.uk> wrote:
> On 07/07/11 02:07, Rusty Russell wrote:
> > On Thu, 7 Jul 2011 10:24:32 +1000, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >> Hi all,
> > ....
> >>> Acked-by: Greg Ungerer <gerg@uclinux.org>
> >>
> >> OK, so now someone just has to remember to apply it (or tell Linus, or
> >> fix up the trees) during the merge window. That person probably won't
> >> be me (since I will not be online next week (assuming Linus follows
> >> through and opens the merge window next week).
> >
> > I'm travelling next week too, so m68k will probably get merged first,
> > and hence I'll roll in this fix myself.
> >
> > Thanks,
> > Rusty.
> Rusty?
>
> If not I'm happy to take on adapting this to meet everyone's requirements.
It's trivial code... just please send to Linus first day of merge
window, and when I rebase I'll fix this up.
Thanks,
Rusty.
next prev parent reply other threads:[~2011-07-21 9:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 3:59 linux-next: manual merge of the rr tree with the tree Stephen Rothwell
2011-07-06 15:57 ` Jonas Bonn
2011-07-06 23:44 ` Greg Ungerer
2011-07-06 23:44 ` Greg Ungerer
2011-07-07 0:24 ` Stephen Rothwell
2011-07-07 0:24 ` Stephen Rothwell
2011-07-07 1:07 ` Rusty Russell
2011-07-19 11:27 ` Jonathan Cameron
2011-07-21 7:55 ` Rusty Russell [this message]
2011-07-25 1:43 ` Stephen Rothwell
2011-07-25 1:43 ` Stephen Rothwell
2011-07-25 2:09 ` Greg Ungerer
2011-07-25 2:09 ` Greg Ungerer
-- strict thread matches above, loose matches on Subject: below --
2009-06-16 3:06 Stephen Rothwell
2009-06-09 3:56 Stephen Rothwell
2009-06-09 9:52 ` 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=8739i02hku.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=jic23@cam.ac.uk \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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.