From: Hugh Dickins <hugh@veritas.com>
To: Andi Kleen <ak@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
acpi-devel@lists.sourceforge.net
Subject: Re: [PATCH] Add CONFIG_X86_APIC_OFF for i386/UP
Date: Fri, 28 Jan 2005 15:46:05 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0501281534420.7304@goblin.wat.veritas.com> (raw)
In-Reply-To: <20050128151839.GI6703@wotan.suse.de>
On Fri, 28 Jan 2005, Andi Kleen wrote:
> > Forgive me for not wading through the code, but it really needs to
> > be spelt out in the comments: what's wrong with the existing kernel,
> > with "noapic nolapic" in the distro's bootstring by default?
>
> It's harder to explain and traditionally in LILO you couldn't remove
> any options (in grub you can now).
And it's just that initial installation boot, via grub, which really
matters. Thereafter can be edited, before perhaps switching to LILO.
> I think it makes much more sense
> to have an positive option for this too, not a negative one.
I do agree that positives are easier to understand than negatives,
and if it were some C variable I'd be arguing the same way.
But we seem to have a long tradition of "no" boot options to disable
features, and you're asking to reverse that tradition: fair enough,
but let's be clear about that. Might be easiest to understand if
every "no" has a no-"no". (But then where does the CONFIG come in?)
> Also I must add my patch fixes real bugs in the code, not just
> adding the new option.
Good, but then they should be in a separate patch.
> > I'm not going to be the only one confused by this!
>
> I think there is much more confusion in the current way.
I'll shut up now, let's see what others think.
Hugh
next prev parent reply other threads:[~2005-01-28 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 13:39 Andi Kleen
2005-01-28 14:27 ` Hugh Dickins
2005-01-28 14:30 ` Andi Kleen
2005-01-28 15:09 ` Hugh Dickins
2005-01-28 15:18 ` Andi Kleen
2005-01-28 15:46 ` Hugh Dickins [this message]
2005-01-28 15:49 ` Andi Kleen
2005-01-28 17:28 ` Adrian Bunk
2005-01-28 17:43 ` Zwane Mwaikambo
2005-01-28 17:46 ` Andi Kleen
2005-01-28 18:30 ` Hugh Dickins
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=Pine.LNX.4.61.0501281534420.7304@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®