From: "Eric S. Raymond" <esr@thyrsus.com>
To: Philip Blundell <philb@gnu.org>
Cc: "Eric S. Raymond" <esr@snark.thyrsus.com>,
torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
trini@kernel.crashing.org, linux-kernel@vger.kernel.org,
kbuild-devel@lists.sourceforge.net
Subject: Re: CML1 cleanup patch, take 3
Date: Mon, 26 Mar 2001 17:22:09 -0500 [thread overview]
Message-ID: <20010326172209.A21538@thyrsus.com> (raw)
In-Reply-To: <200103261924.f2QJOwL19694@snark.thyrsus.com> <esr@snark.thyrsus.com> <E14hf0s-0001Cg-00@kings-cross.london.uk.eu.org>
In-Reply-To: <E14hf0s-0001Cg-00@kings-cross.london.uk.eu.org>; from philb@gnu.org on Mon, Mar 26, 2001 at 10:58:57PM +0100
Philip Blundell <philb@gnu.org>:
> > if [ "$CONFIG_PRINTER" != "n" ]; then
> >- bool ' Support IEEE1284 status readback' CONFIG_PRINTER_READBACK
> >+ bool ' Support IEEE1284 status readback' CONFIG_PARPORT_1284
> > fi
>
> This isn't really right. Although it's true that
> CONFIG_PARPORT_1284 enables the stuff that used to be controlled by
> CONFIG_PRINTER_READBACK, the two aren't synonymous. The m68k port
> ought to just use drivers/parport/Config.in like everybody else.
Yes, I figured this out. The CML2 rules file section for m68k already uses
the normal, architecture-independent parallel-port subtree (some of the
individual options in it are suppressed on certain platforms).
At this point, the only place CONFIG_PRINTER_READBACK actually occurs
seems to be in doc files. So selecting it is a no-op, but one that
obviously means the user wanted the IEEE1284 support. Even given the
two aren't equivalent, I don't see a better way to handle this than the
above. Let's be kind to our 2.4.x users.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
The right of self-defense is the first law of nature: in most
governments it has been the study of rulers to confine this right
within the narrowest limits possible. Wherever standing armies
are kept up, and when the right of the people to keep and bear
arms is, under any color or pretext whatsoever, prohibited,
liberty, if not already annihilated, is on the brink of
destruction."
-- Henry St. George Tucker (in Blackstone's Commentaries)
prev parent reply other threads:[~2001-03-26 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 19:24 CML1 cleanup patch, take 3 Eric S. Raymond
2001-03-26 19:55 ` Jeff Garzik
2001-03-26 20:12 ` Eric S. Raymond
2001-03-26 20:56 ` [kbuild-devel] " John Cowan
2001-03-26 21:09 ` Eric S. Raymond
2001-03-26 21:58 ` Philip Blundell
2001-03-26 22:22 ` Eric S. Raymond [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=20010326172209.A21538@thyrsus.com \
--to=esr@thyrsus.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=esr@snark.thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=philb@gnu.org \
--cc=torvalds@transmeta.com \
--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