* Where did the fs_enet patches go?
@ 2007-09-19 7:05 Esben Haabendal
2007-09-19 7:40 ` Vitaly Bordug
0 siblings, 1 reply; 4+ messages in thread
From: Esben Haabendal @ 2007-09-19 7:05 UTC (permalink / raw)
To: LinuxPPC-dev
Hi
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. :-)
--
Esben Haabendal
Embedded Software Consultant
Doré Development ApS
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Where did the fs_enet patches go?
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
0 siblings, 1 reply; 4+ messages in thread
From: Vitaly Bordug @ 2007-09-19 7:40 UTC (permalink / raw)
To: Esben Haabendal; +Cc: LinuxPPC-dev
Hello Esben,
On Wed, 19 Sep 2007 09:05:16 +0200
Esben Haabendal wrote:
>
> Hi
>
> 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 :)
--
Sincerely, Vitaly
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Where did the fs_enet patches go?
2007-09-19 7:40 ` Vitaly Bordug
@ 2007-09-19 8:25 ` Esben Haabendal
2007-09-19 14:18 ` Scott Wood
0 siblings, 1 reply; 4+ messages in thread
From: Esben Haabendal @ 2007-09-19 8:25 UTC (permalink / raw)
To: Vitaly Bordug, Scott Wood; +Cc: LinuxPPC-dev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Where did the fs_enet patches go?
2007-09-19 8:25 ` Esben Haabendal
@ 2007-09-19 14:18 ` Scott Wood
0 siblings, 0 replies; 4+ messages in thread
From: Scott Wood @ 2007-09-19 14:18 UTC (permalink / raw)
To: Esben Haabendal; +Cc: LinuxPPC-dev
On Wed, Sep 19, 2007 at 10:25:40AM +0200, Esben Haabendal wrote:
> 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 :-)
Ask Jeff. :-)
He asked for examples of clients of the bitbang library, and I provided
them... he never responded.
-Scott
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-09-19 14:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2007-09-19 14:18 ` Scott Wood
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).