From: Paul Bolle <pebolle@tiscali.nl>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
Alan Cox <alan@linux.intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Philip Blundell <philb@gnu.org>
Subject: Re: [PATCH] [TRIVIAL] 8250_hp300: Fix warning typo 'CONFIG_8250'
Date: Thu, 10 Nov 2011 11:22:13 +0100 [thread overview]
Message-ID: <1320920533.27598.67.camel@x61.thuisdomein> (raw)
In-Reply-To: <CAMuHMdVMkLgqjwb7yvFR-tLR2pHcckxkTLDkjNSNjAat9NZ1Mg@mail.gmail.com>
On Wed, 2011-11-09 at 20:52 +0100, Geert Uytterhoeven wrote:
> I have this reminder in my local tree:
>
> diff --git a/arch/m68k/Kconfig.devices b/arch/m68k/Kconfig.devices
> index 6033f5d..354ce91 100644
> --- a/arch/m68k/Kconfig.devices
> +++ b/arch/m68k/Kconfig.devices
> @@ -109,6 +109,7 @@ config MULTIFACE_III_TTY
> To compile this driver as a module, choose M here.
>
> config HPDCA
> + # FIXME Should be bool and select SERIAL_8250_HP300?
> tristate "HP DCA serial support"
> depends on DIO && SERIAL_8250
> help
> @@ -116,6 +117,7 @@ config HPDCA
> machine, say Y here.
>
> config HPAPCI
> + # FIXME Should be bool and select SERIAL_8250_HP300?
> tristate "HP APCI serial support"
> depends on HP300 && SERIAL_8250 && EXPERIMENTAL
> help
>
> However, if these two options are bool, SERIAL_8250_HP300 can never
> be m anymore.
0) This might turn out not to be relevant, but are HPDCA and HPAPCI
exclusive?
> Ah, if we just kill SERIAL_8250_HP300, we can put in the Makefile:
>
> obj-$(CONFIG_HPDCA) += 8250_hp300.o
> obj-$(CONFIG_HPAPCI) += 8250_hp300.o
>
> Does that make sense?
1) Makefiles always make me nervous. What happens if both CONFIG_HPDCA
and CONFIG_HPAPCI are set?
2) This means upgrading both symbols to tristate, doesn't it? It seems
that someone could then end up with this driver builtin instead of as a
module on upgrade (eg, SERIAL_8250_HP300=m and HPDCA=y becomes just
HPDCA=y on upgrade). But I'm not sure whether that is how the config
tools handle symbol upgrades.
3) Does changing the SERIAL_8250_HP300 entry to
config SERIAL_8250_HP300
tristate
depends on HP300 && (HPDCA || HPAPCI)
default SERIAL_8250
work for you? That only changes the "depends on" line.
(If you make HPDCA depend on HP300, which it seems to do in practice,
the dependency on HP300 could also be dropped here.)
Paul Bolle
prev parent reply other threads:[~2011-11-10 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 13:44 Paul Bolle
2011-11-08 9:26 ` Jiri Kosina
2011-11-08 9:34 ` Paul Bolle
2011-11-08 10:32 ` Geert Uytterhoeven
2011-11-09 19:52 ` Geert Uytterhoeven
2011-11-10 10:22 ` Paul Bolle [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=1320920533.27598.67.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=alan@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=philb@gnu.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
all inboxes | Powered by JetHome®