From: Scott Wood <scottwood@freescale.com>
To: Alexandros Kostopoulos <akostop@inaccessnetworks.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: About mdio_bus for 82xx based board
Date: Thu, 26 Jul 2007 10:29:37 -0500 [thread overview]
Message-ID: <46A8BDE1.8080900@freescale.com> (raw)
In-Reply-To: <op.tv2nbmkonhx3hy@phoenix>
Alexandros Kostopoulos wrote:
> Well, I've downloaded the latest git from Paul's tree, and some patches
> still fail (and the mpc8272_ads config doesn't compile). Must I get
> some other revision of the tree (if yes, how's that done in git - my
> first time with it )
They don't apply on top of Paul's current tree -- they apply to his tree
as of the time the patchset was posted. I should have a revised
patchset in a week or two (the delay mainly being to add and test a
couple new boards).
-Scott
prev parent reply other threads:[~2007-07-26 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 14:22 About mdio_bus for 82xx based board Alexandros Kostopoulos
2007-07-25 16:23 ` Scott Wood
2007-07-26 10:42 ` Alexandros Kostopoulos
2007-07-26 11:24 ` Alexandros Kostopoulos
2007-07-26 12:22 ` Alexandros Kostopoulos
2007-07-26 15:29 ` Scott Wood [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=46A8BDE1.8080900@freescale.com \
--to=scottwood@freescale.com \
--cc=akostop@inaccessnetworks.com \
--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).