All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: benh@kernel.crashing.org
Cc: netdev@vger.kernel.org, Stefan Roese <sr@denx.de>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] net: NEWEMAC: Support for Pause packets in EMAC driver
Date: Mon, 17 Mar 2008 18:31:53 -0400	[thread overview]
Message-ID: <47DEF159.3020504@garzik.org> (raw)
In-Reply-To: <1205790747.26869.187.camel@pasglop>

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.

	Jeff

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jeff@garzik.org>
To: benh@kernel.crashing.org
Cc: Josh Boyer <jwboyer@linux.vnet.ibm.com>,
	Stefan Roese <sr@denx.de>,
	netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Valentine Barshak <vbarshak@ru.mvista.com>
Subject: Re: [PATCH] net: NEWEMAC: Support for Pause packets in EMAC driver
Date: Mon, 17 Mar 2008 18:31:53 -0400	[thread overview]
Message-ID: <47DEF159.3020504@garzik.org> (raw)
In-Reply-To: <1205790747.26869.187.camel@pasglop>

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.

	Jeff




  reply	other threads:[~2008-03-17 22:32 UTC|newest]

Thread overview: 25+ 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-14  9:52 ` Stefan Roese
2008-03-17 12:08 ` Jeff Garzik
2008-03-17 12:08   ` Jeff Garzik
2008-03-17 21:25   ` Benjamin Herrenschmidt
2008-03-17 21:25     ` Benjamin Herrenschmidt
2008-03-17 21:26     ` Benjamin Herrenschmidt
2008-03-17 21:26       ` Benjamin Herrenschmidt
2008-03-17 21:43       ` Josh Boyer
2008-03-17 21:43         ` Josh Boyer
2008-03-17 21:52         ` Benjamin Herrenschmidt
2008-03-17 22:31           ` Jeff Garzik [this message]
2008-03-17 22:31             ` Jeff Garzik
2008-03-17 23:55             ` Benjamin Herrenschmidt
2008-03-17 23:55               ` Benjamin Herrenschmidt
2008-03-18  1:08             ` Josh Boyer
2008-03-18  1:08               ` Josh Boyer
2008-03-18  2:41               ` Benjamin Herrenschmidt
2008-03-18  3:56                 ` Josh Boyer
2008-03-18  3:56                   ` Josh Boyer
2008-03-18  4:06                 ` Jeff Garzik
2008-03-18  4:06                   ` Jeff Garzik
2008-03-18  5:35                   ` Benjamin Herrenschmidt
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=47DEF159.3020504@garzik.org \
    --to=jeff@garzik.org \
    --cc=benh@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.