From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc_2_4_devel patch: 8xx FEC extensions
Date: Sat, 28 Dec 2002 01:27:45 +0100 [thread overview]
Message-ID: <20021228002750.B4A70C6139@atlas.denx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
In message <20021223151254.GC15397@opus.bloom.county> you wrote:
>
> > It makes the following modifications to the MPC8xx FEC driver:
> >
> > - change PHY configuration from #define to kernel config mechanism
> > - add support for AMD79C874 PHY
>
> Both of these look OK, but can you please split this out into a seperate
> patch which just does PHY configuration and then adds AMD79C874 support?
Of course I can.
PHY configuration ==> patch.1
add AMD79C874 support ==> patch.2
> > - add multicast support
>
> Sounds fine, but can you split this portion of the code from the rest of
> the patch please? Thanks.
Of course I can.
cleanup & add multicast support ==> patch.3
But really, why do I have to do this?
I'm pretty sure you can read the patch as is so you are able to
either complain about stuff you don't like or to accept these things
in one patch. Is this just some form of bullying, or is there a
rational reason behind this requirement?
> > - add PACKETHOOK support
>
> This was removed, intentionally back on March 22nd, 2002. From what I
> recall, it was decided this code was broken / unmaintained and should be
> yanked. Have you tested this particular section of code to verify it
> still compiles and works as expected?
>
> In sum: On hold for now.
If that was a decision I'm not in the position to discuss such a
things. Just forget it.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The complexity of software is an essential property, not an acciden-
tal one. Hence, descriptions of a software entity that abstract away
its complexity often abstract away its essence. - Fred Brooks, Jr.
[-- Attachment #2: 8xx-fec.patches.tar.gz --]
[-- Type: application/x-gzip , Size: 7964 bytes --]
next prev reply other threads:[~2002-12-28 0:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 1:05 linuxppc_2_4_devel patch: 8xx FEC extensions Wolfgang Denk
2002-12-23 15:12 ` Tom Rini
2002-12-28 0:27 ` Wolfgang Denk [this message]
2002-12-30 15:29 ` Tom Rini
2002-12-30 16:26 ` Wolfgang Denk
2002-12-30 18:12 ` Tom Rini
[not found] ` <3E10EF1C.5040505@embeddededge.com>
[not found] ` <20021231155241.GA12063@opus.bloom.county>
[not found] ` <20021231155839.6D6F8C6139@atlas.denx.de>
2002-12-31 16:13 ` Tom Rini
2003-01-02 17:40 ` Wolfgang Denk
[not found] ` <3E1480E6.4010802@embeddededge.com>
2003-01-02 18:21 ` Tom Rini
[not found] ` <3E1484D9.6070402@embeddededge.com>
2003-01-03 15:47 ` Tom Rini
2003-01-02 17:40 ` Dan Malek
2003-01-03 22:46 ` Paul Mackerras
2003-01-03 23:01 ` Dan Malek
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=20021228002750.B4A70C6139@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).