public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] ppc32: Update 8260_io/fcc_enet.c to function again
Date: Wed, 16 Mar 2005 13:43:20 -0500	[thread overview]
Message-ID: <42387E48.1090902@pobox.com> (raw)
In-Reply-To: <20050315182537.GW8345@smtp.west.cox.net>

Tom Rini wrote:
> There's too many things in here that've sat too long (I'd been hoping to
> just delete the driver, but that hasn't happened yet, so).  A cobbled
> together list of changes is:
> 
> - Update MDIO support for workqueues.
> - Make use of <linux/mii.h>
> - Add RPX6 support.
> - Comment out set_multicast_list (broken).
> - Rework tx_ring stuff so we have tx_free, not tx_Full/n_pkts.
> - Other PHY updates/fixes.
> - Leo Li: Rework FCC clock configuration, make it easier.
> - 2.4 : VLAN header room, other misc bits.
> - Kill MII_REG_NNN in favor of defines from <linux/mii.h>
> - DM9161 PHY support (2.4, Myself & alebas@televes.com)
> - PQ2ADS and PQ2FADS support bits (Myself & alebas@televes.com

Please make sure I and netdev@oss.sgi.com are CC'd on all net driver 
patches.

Also, it would be nice to move this into drivers/net/*

	Jeff



  parent reply	other threads:[~2005-03-16 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 18:25 [PATCH] ppc32: Update 8260_io/fcc_enet.c to function again Tom Rini
2005-03-16  6:31 ` Andrew Morton
2005-03-16 18:43 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-16  8:00 Bastos Fernandez Alexandre
2005-03-16 14:54 ` Tom Rini
2005-03-16 15:04 Balasaygun, Oray (Oray)

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=42387E48.1090902@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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