netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geoff Levand <geoffrey.levand@am.sony.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"Geert.Uytterhoeven" <Geert.Uytterhoeven@sonycom.com>,
	netdev@vger.kernel.org,
	Linux/PPC Development <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 0/6] PS3: gelic: gelic updates for 2.6.25
Date: Tue, 22 Jan 2008 19:12:44 -0800	[thread overview]
Message-ID: <4796B0AC.5060205@am.sony.com> (raw)
In-Reply-To: <20080123005845.GE3206@tuxdriver.com>

On 01/22/2008 04:58 PM, John W. Linville wrote:
> On Wed, Jan 23, 2008 at 11:40:34AM +1100, Benjamin Herrenschmidt wrote:
>> 
>> On Tue, 2008-01-22 at 16:12 -0500, John W. Linville wrote:
>> > On Thu, Dec 13, 2007 at 07:38:28PM +0900, Masakazu Mokuno wrote:
>> > 
>> > > Here is a set of updates for PS3 gelic network driver.
>> > > This patch set requires other patches which were already submitted by
>> > > Geert (http://marc.info/?l=linux-kernel&m=119626095605487).
>> > > 
>> > > 	[1] PS3: gelic: Fix the wrong dev_id passed
>> > > 	[2] PS3: gelic: Add endianness macros
>> > > 	[3] PS3: gelic: Code cleanup
>> > > 	[4] PS3: gelic: Remove duplicated ethtool handers
>> > > 	[5] PS3: gelic: Add support for port link status
>> > > 	[6] PS3: gelic: Add support for dual network interface
>> > > 
>> > > This is also a set of prerequisite for new wireless driver for PS3, which
>> > > I'll submit later. 
>> > 
>> > These seem to not have been applied, but I couldn't find any stated
>> > reason.  Did they just get lost?  Withdrawn?
>> > 
>> > Will these be applied?  There is a wireless patch that depends on them.
>> > If not, will the wireless portion be refactored to not require these
>> > patches?
>> 
>> The list of 6 patches above are the patches that Masakazu Mukono is
>> submitting, the pre-reqs are different patches (see the linked URL),
>> though I can't see them in either (they should probably go through
>> paulus for-2.6.25). Geert, what's up with these ?
> 
> The wireless patch depends on the patches 1-6, which then depend on
> Geert's patches.
> 
> I thought Geert's had been applied, but I guess I was looking at
> it wrong.  Is there a powerpc tree that has them?

Not yet, they are now only in ps3-linux.git.  I sent them out to
Paul last Friday the 18th for inclusion in 2.6.25.  Here is a link
to the message:

  http://ozlabs.org/pipermail/linuxppc-dev/2008-January/050213.html

> Perhaps 1-6 above
> and the wireless patch should just be applied to that tree (if there
> is one) and all merged together?

I think Paul will accept them if they have the Sign-off-by's of
the proper network maintainers.

-Geoff


  reply	other threads:[~2008-01-23  3:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 10:38 [PATCH 0/6] PS3: gelic: gelic updates for 2.6.25 Masakazu Mokuno
2007-12-13 12:05 ` [PATCH 1/6] PS3: gelic: Fix the wrong dev_id passed Masakazu Mokuno
2007-12-13 12:07 ` [PATCH 2/6] PS3: gelic: Add endianness macros Masakazu Mokuno
2007-12-13 12:09 ` [PATCH 3/6] PS3: gelic: code cleanup Masakazu Mokuno
2007-12-13 12:11 ` [PATCH 4/6] PS3: gelic: remove duplicated ethtool handers Masakazu Mokuno
2007-12-13 12:13 ` [PATCH 5/6] PS3: gelic: add support for port link status Masakazu Mokuno
2007-12-13 12:16 ` [PATCH 6/6] PS3: gelic: Add support for dual network interface Masakazu Mokuno
2008-01-24  5:41   ` [PATCH 6/6 v2] " Masakazu Mokuno
2008-01-22 21:12 ` [PATCH 0/6] PS3: gelic: gelic updates for 2.6.25 John W. Linville
2008-01-23  0:40   ` Benjamin Herrenschmidt
2008-01-23  0:58     ` John W. Linville
2008-01-23  3:12       ` Geoff Levand [this message]
2008-01-24  2:36         ` John W. Linville
2008-01-30  5:21 ` Masakazu Mokuno

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=4796B0AC.5060205@am.sony.com \
    --to=geoffrey.levand@am.sony.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.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).