From: Dan Malek <dan@embeddededge.com>
To: acurtis@onz.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: FCC patch..really
Date: Wed, 28 Aug 2002 01:29:38 -0400 [thread overview]
Message-ID: <3D6C5FC2.1090204@embeddededge.com> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFMEEJDLAA.acurtis@onz.com
Allen Curtis wrote:
> I have another update that does the same thing with the MDIO lines per PHY
> ;)
Please don't. This stuff doesn't belong in configuration files. There is
nothing wrong with creating platform specific configuration in files
that can be compiled and using a single configuration option and #define to
make this happen. Cluttered configuration scripts are a source of error
and headache.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-28 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 0:08 FCC patch..really Allen Curtis
2002-08-28 3:52 ` Dan Malek
2002-08-28 4:11 ` Allen Curtis
2002-08-28 5:29 ` Dan Malek [this message]
2002-08-28 14:43 ` Allen Curtis
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=3D6C5FC2.1090204@embeddededge.com \
--to=dan@embeddededge.com \
--cc=acurtis@onz.com \
--cc=linuxppc-embedded@lists.linuxppc.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).