From: Keith Owens <kaos@ocs.com.au>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Frank Davis <fdavis112@juno.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.5-ac4 es1371.o unresolved symbols
Date: Thu, 31 May 2001 18:34:20 +1000 [thread overview]
Message-ID: <17420.991298060@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 31 May 2001 10:06:54 +0200." <20010531100654.A1759@suse.cz>
On Thu, 31 May 2001 10:06:54 +0200,
Vojtech Pavlik <vojtech@suse.cz> wrote:
>On Thu, May 31, 2001 at 05:52:39PM +1000, Keith Owens wrote:
>> When the user has gameport hardware compiled it as a module and they
>> have es1371 bult into the kernel then es1371 silently ignores the
>> gameport, even if the gameport modules has been loaded. This violates
>> the principle of least surprise, a user configuring both gameport and
>> es1371 expects to use the gameport, kbuild should support that instead
>> of silently ignoring the combination.
>
>True. Is this worse than the ugliness in your patch?
Only kernel developers see the ugly patch. The unexpected presence or
absence of gameport code affects all users. User always win that
argument. Adding a warning is just as bad, kbuild either generates a
valid config or nothing at all. Users never check warnings anyway :(.
prev parent reply other threads:[~2001-05-31 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 1:56 2.4.5-ac4 es1371.o unresolved symbols Frank Davis
2001-05-30 2:22 ` Keith Owens
2001-05-30 4:46 ` Keith Owens
2001-05-30 16:15 ` Vojtech Pavlik
2001-05-31 1:29 ` Keith Owens
2001-05-31 6:08 ` Vojtech Pavlik
2001-05-31 7:52 ` Keith Owens
2001-05-31 8:06 ` Vojtech Pavlik
2001-05-31 8:13 ` Vojtech Pavlik
2001-05-31 8:34 ` Keith Owens [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=17420.991298060@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fdavis112@juno.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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