netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentine Barshak <vbarshak@ru.mvista.com>
To: benh@kernel.crashing.org
Cc: netdev@vger.kernel.org, Stefan Roese <sr@denx.de>,
	Jeff Garzik <jeff@garzik.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] net: NEWEMAC: Support for Pause packets in EMAC driver
Date: Tue, 18 Mar 2008 17:21:56 +0300	[thread overview]
Message-ID: <47DFD004.4000202@ru.mvista.com> (raw)
In-Reply-To: <1205808100.26869.204.camel@pasglop>

Benjamin Herrenschmidt wrote:
>> http://marc.info/?l=linux-netdev&m=120449748701492&w=2
>>
>> I sent it to Ben with netdev on CC because you asked the various people
>> sending NEWEMAC patches to you to find a single person.
>>
>> So from now on, what are we going to do?  It seems we're playing net
>> maintainer russian roulette for NEWEMAC and it's getting old.
> 
> I'm happy to collect the patches. I said I would do it, I was just taken
> aback a bit by Jeff suddenly merging two of Stefan patches directly :-)
> 
> I was actually planning this week to post a serie of all the pending
> EMAC patches for final review.
> 
> Cheers,
> Ben.
> 
> 

FYI, These are the NEWEMAC patches I've sent:
http://ozlabs.org/pipermail/linuxppc-dev/2008-February/052114.html
(This is a TAH csum fix, that I don't see on the patchwork for some reason)
and a couple of PHY clock workarounds
http://patchwork.ozlabs.org/linuxppc/patch?id=17211
http://patchwork.ozlabs.org/linuxppc/patch?id=17212
The latter two patches depend on the "dcri_clrset" one:
http://patchwork.ozlabs.org/linuxppc/patch?id=17199
Ben, could you please also take a look at the PCIe dcri_clrset stuff here
http://patchwork.ozlabs.org/linuxppc/patch?id=17214
(not EMAC related)
Thanks,
Valentine.

      parent reply	other threads:[~2008-03-18 14:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  9:52 [PATCH] net: NEWEMAC: Support for Pause packets in EMAC driver Stefan Roese
2008-03-17 12:08 ` Jeff Garzik
2008-03-17 21:25   ` Benjamin Herrenschmidt
2008-03-17 21:26     ` Benjamin Herrenschmidt
2008-03-17 21:43       ` Josh Boyer
2008-03-17 21:52         ` Benjamin Herrenschmidt
2008-03-17 22:31           ` Jeff Garzik
2008-03-17 23:55             ` Benjamin Herrenschmidt
2008-03-18  1:08             ` Josh Boyer
2008-03-18  2:41               ` Benjamin Herrenschmidt
2008-03-18  3:56                 ` Josh Boyer
2008-03-18  4:06                 ` Jeff Garzik
2008-03-18  5:35                   ` Benjamin Herrenschmidt
2008-03-18 14:21                 ` Valentine Barshak [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=47DFD004.4000202@ru.mvista.com \
    --to=vbarshak@ru.mvista.com \
    --cc=benh@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=sr@denx.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).