From: Grant Likely <grant.likely@secretlab.ca>
To: "Albrecht Dreß" <albrecht.dress@arcor.de>
Cc: linuxppc-dev@ozlabs.org, agust@denx.de
Subject: Re: mpc512x uart: testers wanted
Date: Fri, 26 Mar 2010 20:10:36 -0600 [thread overview]
Message-ID: <fa686aa41003261910uf5c3612pf275d034237ba997@mail.gmail.com> (raw)
In-Reply-To: <fa686aa41003080853q521b4f81s5c7488ebcc8dfb63@mail.gmail.com>
On Mon, Mar 8, 2010 at 9:53 AM, Grant Likely <grant.likely@secretlab.ca> wr=
ote:
> On Mon, Mar 8, 2010 at 9:32 AM, Albrecht Dre=DF <albrecht.dress@arcor.de>=
wrote:
>> Hi Anatolij:
>>
>>> > Anatolij, could you please look into this?
>>>
>>> I'll look into this tomorrow, need to finish USB support now.
>>> Unfortunately the patch doesn't apply on top of Linus' tree as
>>> patches for reworked MPC5121 PSC UART support have been merged.
>>> Albrecht, could you please rebase your patch?
>>
>> Against linux/kernel/git/torvalds/linux-2.6.git? =A0Will do that tomorro=
w... =A0Grant, do you need a patch against Linus' tree, or against a releas=
ed version, or against your tree?
>
> I won't be picking this up until after -rc1 or -rc2 anyway, and it
> won't get merged into Linus' tree until the 2.6.35 merge window, so
> I'm not going to even touch it for a couple of weeks. =A0When I do get
> to it I'll need it against Linus' tree.
Ping? I was looking at this tonight but it of course doesn't apply.
Have you gotten a chance to rebase this patch yet?
Thanks,
g.
next prev parent reply other threads:[~2010-03-27 2:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 16:15 mpc512x uart: testers wanted Albrecht Dreß
2010-03-08 0:45 ` Grant Likely
2010-03-08 14:19 ` Anatolij Gustschin
2010-03-08 16:32 ` Albrecht Dreß
2010-03-08 16:53 ` Grant Likely
2010-03-27 2:10 ` Grant Likely [this message]
2010-03-27 13:29 ` Albrecht Dreß
2010-03-27 14:33 ` Grant Likely
2010-03-27 17:47 ` Wolfgang Denk
[not found] <1272392908.6504.0@antares>
2010-05-02 11:24 ` Albrecht Dreß
2010-05-02 14:23 ` Grant Likely
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=fa686aa41003261910uf5c3612pf275d034237ba997@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=agust@denx.de \
--cc=albrecht.dress@arcor.de \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).