linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: jengelh@linux01.gwdg.de,
	"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: drivers/net/fec_8xx config problem
Date: Thu, 1 May 2008 09:47:38 +0400	[thread overview]
Message-ID: <20080501094738.13dca29a@vitb-lp> (raw)
In-Reply-To: <20080430192329.GA9150@ld0162-tx32.am.freescale.net>

On Wed, 30 Apr 2008 14:23:29 -0500
Scott Wood wrote:

> On Wed, Apr 30, 2008 at 02:24:19PM -0500, Becky Bruce wrote:
> > 
> > On Apr 30, 2008, at 2:20 PM, Scott Wood wrote:
> > >On Wed, Apr 30, 2008 at 02:19:21PM -0500, Becky Bruce wrote:
> > >>I just noticed that the fec_8xx driver is not currently reachable
> > >>via menuconfig because it depends on 8XX instead of 8xx.
> > >[snip]
> > >>Since nobody has noticed this problem, I'm wondering if this
> > >>driver is still in (infrequent) use, or if it's been superseded
> > >>and should be removed, or if I'm just completely missing
> > >>something with respect to the use of "8XX" instead of "8xx".
> > >
> > >It's been superseded by drivers/net/fs_enet.
> > 
> > Is there any reason we haven't removed it?
> 
> To keep arch/ppc/8xx_io company? :-)
> 
> > If not, I can push a patch to yank it.
> 
> I have no objection.

I am OK with this too. Should have been done long ago, but who likes janitorial stuff :)

-Vitaly

      parent reply	other threads:[~2008-05-01  6:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 19:19 drivers/net/fec_8xx config problem Becky Bruce
2008-04-30 19:20 ` Scott Wood
2008-04-30 19:24   ` Becky Bruce
2008-04-30 19:23     ` Scott Wood
2008-04-30 20:21       ` Jan Engelhardt
2008-05-01  5:47       ` Vitaly Bordug [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=20080501094738.13dca29a@vitb-lp \
    --to=vitb@kernel.crashing.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).