From: Arjan van de Ven <arjanv@redhat.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Arjan van de Ven'" <arjanv@redhat.com>,
marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] ACPI updates
Date: Tue, 3 Dec 2002 18:00:52 -0500 [thread overview]
Message-ID: <20021203180052.B7885@devserv.devel.redhat.com> (raw)
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A56B@orsmsx119.jf.intel.com>; from andrew.grover@intel.com on Tue, Dec 03, 2002 at 10:39:18AM -0800
On Tue, Dec 03, 2002 at 10:39:18AM -0800, Grover, Andrew wrote:
> The ACPI code's CPU-enumeration-only config option does what acpitable.[ch]
> did.
With a lot more code.
> Is your concern with the code, or the cmdline option? We could certainly
the code, not so much the commandline option (that one is not used
in practice), but actually my biggest concern is that you break existing
setups, or at least change it more than needed. There is ZERO need to
remove the existing working (and lean) code, even though your code might
also be able to do the same. It means people suddenly need to change all
kinds of config options, it's different code so will work slightly
different... unifying 2.5 is nice and all but there's no need for that
here since both implementations can coexist trivially (as the United Linux
kernel shows)
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2002-12-03 22:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 18:39 Grover, Andrew
2002-12-03 19:31 ` Alan Cox
2002-12-03 23:00 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-24 0:15 Grover, Andrew
2002-12-06 1:36 Grover, Andrew
2002-12-06 16:50 ` Pavel Machek
2002-12-03 23:29 Grover, Andrew
2002-12-03 23:47 ` Arjan van de Ven
2002-12-04 12:58 ` Dave Jones
2002-12-05 17:06 ` Pavel Machek
2002-12-02 19:29 Grover, Andrew
2002-12-03 9:31 ` Arjan van de Ven
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=20021203180052.B7885@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
Powered by JetHome