From: Tony Lindgren <tony@atomide.com>
To: Alistair Buxton <a.j.buxton@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [RFC] OMAP1: Massive clean up of omap730/omap850 code
Date: Wed, 7 Oct 2009 10:54:11 -0700 [thread overview]
Message-ID: <20091007175410.GH7899@atomide.com> (raw)
In-Reply-To: <3d374d00909281419v1b4bf578sdb883371655492bb@mail.gmail.com>
* Alistair Buxton <a.j.buxton@gmail.com> [090928 14:19]:
> 2009/9/23 Tony Lindgren <tony@atomide.com>:
> >
> > Thanks, looks good to me.
> >
> > Can you please rebase against the mainline 2.6.32-rc1 once it gets
> > tagged?
> >
> > Then please keep your branch around until it all gets merged into the
> > mainline tree. There should not be any need for you to rebase it,
> > but I may need to pull it several times as I rebase the various
> > upstream queues after each -rc.
>
> Done. ZMC has now reviewed it, and I've mirrored it to a proper hosted
> server too:
>
> git://robotfuzz.com/linwizard-kernel.git
> branch: omap7xx-fortony-rc1
>
> Confirmed booting to a shell with the addition of the patches in
> branch omap7xx-test2 - but those patches aren't ready to go as we
> still need workarounds for a serial bug in order to know that we have
> booted.
Can you please rebase on v2.6.32-rc3 and let me know when you have
your new branch ready? There's one merge conflict merging that branch
from -rc1, I've kind of tweaked my scripts to work around that but
it still needs manual merging ;)
Regards,
Tony
next prev parent reply other threads:[~2009-10-07 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 4:07 [RFC] OMAP1: Massive clean up of omap730/omap850 code Alistair Buxton
2009-09-21 23:17 ` Tony Lindgren
2009-09-23 18:26 ` Alistair Buxton
2009-09-23 22:21 ` Tony Lindgren
2009-09-28 21:19 ` Alistair Buxton
2009-10-07 17:54 ` Tony Lindgren [this message]
2009-10-14 0:52 ` Tony Lindgren
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=20091007175410.GH7899@atomide.com \
--to=tony@atomide.com \
--cc=a.j.buxton@gmail.com \
--cc=linux-omap@vger.kernel.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.