From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: NEWEMAC: Support for Pause packets in EMAC driver
Date: Mon, 17 Mar 2008 20:08:55 -0500 [thread overview]
Message-ID: <20080317200855.2954971a@zod.rchland.ibm.com> (raw)
In-Reply-To: <47DEF159.3020504@garzik.org>
On Mon, 17 Mar 2008 18:31:53 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> Benjamin Herrenschmidt wrote:
> >> There's also the section mismatch patch I sent you. I don't care who's
> >> tree they go through, but I'd need to know either way so keep me in the
> >> loop please.
> >
> > Jeff, do you mind if we get those patches through the powerpc tree ?
> > EMAC is very powerpc specific and these are mostly internal driver
> > cuisine.
>
> Fine with me in concept, though I haven't seen the patches in question.
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.
josh
next prev parent reply other threads:[~2008-03-18 1:09 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 [this message]
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
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=20080317200855.2954971a@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--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).