linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Esben Haabendal <eha@doredevelopment.dk>
To: Vitaly Bordug <vitb@kernel.crashing.org>,
	Scott Wood <scottwood@freescale.com>
Cc: LinuxPPC-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Where did the fs_enet patches go?
Date: Wed, 19 Sep 2007 10:25:40 +0200	[thread overview]
Message-ID: <8406613ce51e309ebffa430dcec8bbf6@127.0.0.1> (raw)
In-Reply-To: <20070919114035.075acafb@localhost.localdomain>


On Wed, 19 Sep 2007 11:40:35 +0400, Vitaly Bordug <vitb@kernel.crashing.org> wrote:
> On Wed, 19 Sep 2007 09:05:16 +0200
>> Where did the patches containing the reworked fs_enet drivers and the
>> generic bitbanged MDIO library go?
>> I am talking about these 8 patches:
>> http://www.mail-archive.com/linuxppc-dev@ozlabs.org/msg03184.html
>>
>> They seem to have been removed from
>> http://patchwork.ozlabs.org/linuxppc/ ...
>>
>> AFAICS, they have not been merged in neither galak or paulus git.
>>
>> It works nicely here at my mpc8270 target btw. :-)
>>
> iirc they are slowly spinning with netdev/Jeff Garzik... Scott would know
> for sure :)

Ah, I see. Thanks.

Most of it is at least ack'ed by Jeff. But he did not seem to like
the generic bitbanged MDIO library.
Scott, what is the plan with that part?  I need it :-)

/Esben
-- 
Esben Haabendal
Embedded Software Consultant
Doré Development ApS

  reply	other threads:[~2007-09-19  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  7:05 Where did the fs_enet patches go? Esben Haabendal
2007-09-19  7:40 ` Vitaly Bordug
2007-09-19  8:25   ` Esben Haabendal [this message]
2007-09-19 14:18     ` Scott Wood

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=8406613ce51e309ebffa430dcec8bbf6@127.0.0.1 \
    --to=eha@doredevelopment.dk \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=vitb@kernel.crashing.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).