From: Rogan Dawes <lists@dawes.za.net>
To: Adrian Bunk <bunk@kernel.org>
Cc: chris@zankel.net, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] xtensa: don't offer PARPORT_PC
Date: Mon, 14 Apr 2008 22:33:33 +0200 [thread overview]
Message-ID: <4803BF9D.4070304@dawes.za.net> (raw)
In-Reply-To: <20080414195551.GE26885@cs181133002.pp.htv.fi>
Adrian Bunk wrote:
> config PARPORT_PC
> tristate "PC-style hardware"
> depends on (!SPARC64 || PCI) && !SPARC32 && !M32R && !FRV && \
> - (!M68K || ISA) && !MN10300
> + (!M68K || ISA) && !MN10300 && !XTENSA
Pardon a possibly stupid question here, but would it not make more sense
to code the architectures for which these various devices *are*
possible, rather than requiring each architecture to go through the
entire config file and add their own "we don't do this" for many entries?
As seen, it is easy for them to be missed, hence all these recent patches.
The way I look at it, it is a lot easier to require that the arch
maintainer adds specific entries to get their particular hardware
working, rather than go through a working setup and figure out how much
they can take away before it breaks.
Rogan
next prev parent reply other threads:[~2008-04-14 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 19:55 [2.6 patch] xtensa: don't offer PARPORT_PC Adrian Bunk
2008-04-14 20:33 ` Rogan Dawes [this message]
2008-04-14 21:34 ` Alan Cox
2008-04-14 21:31 ` Alan Cox
2008-04-14 22:13 ` Adrian Bunk
2008-04-14 23:00 ` Chris Zankel
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=4803BF9D.4070304@dawes.za.net \
--to=lists@dawes.za.net \
--cc=bunk@kernel.org \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.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