From: Dave Jones <davej@suse.de>
To: Brad Hards <bhards@bigpond.net.au>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
"'Pavel Machek'" <pavel@suse.cz>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
trivial@rustcorp.com.au
Subject: Re: [patch] i386 "General Options" - begone [take 2]
Date: Wed, 5 Jun 2002 12:29:39 +0200 [thread overview]
Message-ID: <20020605122939.H5277@suse.de> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7ED5@orsmsx111.jf.intel.com> <200206051134.24063.bhards@bigpond.net.au>
On Wed, Jun 05, 2002 at 11:34:23AM +1000, Brad Hards wrote:
> One idea that comes to mind is putting the power management config options in
> a "Power Management" section
*nod* sounds sensible 8)
> then PNPBIOS in with the other PnP stuff, and
> so on (read: don't know were to put MPS yet, and don't know what $PIR is :)
It's an interrupt routing table.
MPS and interrupt routing are both CPU related features, so the best
place we currently have is under the CPU menu imho.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-06-05 10:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 20:59 [patch] i386 "General Options" - begone [take 2] Grover, Andrew
2002-06-04 21:20 ` Dave Jones
2002-06-05 1:34 ` Brad Hards
2002-06-05 10:29 ` Dave Jones [this message]
2002-06-05 23:11 ` Brad Hards
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 23:31 Grover, Andrew
2002-06-04 23:09 Grover, Andrew
2002-06-04 23:25 ` Dave Jones
2002-06-05 1:00 ` Alan Cox
2002-06-04 21:58 Grover, Andrew
2002-06-04 22:09 ` Dave Jones
2002-06-04 23:16 ` Alan Cox
2002-06-07 5:38 ` fchabaud
2002-06-03 1:56 Linux 2.5.20 Linus Torvalds
2002-06-03 3:18 ` [patch] i386 "General Options" - begone [take 2] Brad Hards
2002-06-03 22:42 ` Rusty Russell
2002-06-04 14:09 ` Pavel Machek
2002-06-04 22:05 ` Brad Hards
2002-06-02 5:16 ` Pavel Machek
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=20020605122939.H5277@suse.de \
--to=davej@suse.de \
--cc=andrew.grover@intel.com \
--cc=bhards@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.com \
--cc=trivial@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.