From: Grant Likely <grant.likely@secretlab.ca>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull 'next' branch of git://git.secretlab.ca/git/linux-2.6-mpc52xx
Date: Wed, 15 Oct 2008 08:34:19 -0600 [thread overview]
Message-ID: <20081015143419.GH16262@secretlab.ca> (raw)
In-Reply-To: <20081014133346.GE23594@pengutronix.de>
On Tue, Oct 14, 2008 at 03:33:46PM +0200, Wolfram Sang wrote:
> What about these? :)
>
> http://oldpatchwork.ozlabs.org/linuxppc-embedded/patch?id=20188
> (remove obsolete code from mpc52xx_phy)
I'm not going to pick this one up yet (as mentioned in my earlier
email)
> http://oldpatchwork.ozlabs.org/linuxppc-embedded/patch?id=20189
> (simplify read/write in mpc52xx_phy)
> http://oldpatchwork.ozlabs.org/linuxppc-embedded/patch?id=20202
> (don't touch pipelining)
Both of these are in my tree and I'll be asking Ben to pull soon.
> And to which tree did this one go? I couldn't find it on
> git.secretlab.ca.
In the 'next' branch of my mpc52xx tree.
g.
prev parent reply other threads:[~2008-10-15 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 8:02 Please pull 'next' branch of git://git.secretlab.ca/git/linux-2.6-mpc52xx Grant Likely
2008-10-14 13:33 ` Wolfram Sang
2008-10-15 14:34 ` Grant Likely [this message]
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=20081015143419.GH16262@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=w.sang@pengutronix.de \
/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).