From: Scott Wood <scottwood@freescale.com>
To: raul.moreno@telvent.abengoa.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 2.6.22-ppc8xx fec.c bugs
Date: Thu, 10 Jan 2008 11:48:48 -0600 [thread overview]
Message-ID: <47865A80.7050205@freescale.com> (raw)
In-Reply-To: <OF7BC7CA29.9B371169-ONC12573CC.00553A44-C12573CC.0057BA09@abengoa.com>
raul.moreno@telvent.abengoa.com wrote:
> Hello everyone,
>
> I don't know who the maintainer of the FEC (Fast Ethernet Controller) in
> the ppc8xx achitecture is, so I am writing this email here.
arch/ppc is deprecated, and arch/ppc/8xx_io especially so.
Please use drivers/net/fs_enet (and also note that arch/ppc will be
going away in a few months).
> I've seen that some bugs were fixed in the latest kernel but others haven't
> been addressed (possibly undetected yet). The following is a diff with
> corrections I made to the 2.6.22 'fec.c' file (currently seems to work
> fine).
Please post patches against the latest head-of-tree, and in unified diff
format (diff -u).
-Scott
next prev parent reply other threads:[~2008-01-10 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:33 kernel panic after upgrading to 2.6.22 raul.moreno
2008-01-10 15:57 ` 2.6.22-ppc8xx fec.c bugs raul.moreno
2008-01-10 17:48 ` Scott Wood [this message]
2008-01-11 8:51 ` raul.moreno
2008-01-11 17:27 ` Scott Wood
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=47865A80.7050205@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=raul.moreno@telvent.abengoa.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).