linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] sanitize power management config menus
Date: Sun, 27 Jul 2003 04:56:47 +0200	[thread overview]
Message-ID: <20030727025647.GB17724@louise.pinerecords.com> (raw)
In-Reply-To: <20030726194651.5e3f00bb.rddunlap@osdl.org>

> [rddunlap@osdl.org]
> 
> 1.  However, both old and new versions say:
>   Power management options (ACPI, APM)  --->
> but have Software Suspend and CPU Frequency (hidden) below there,
> so one has to know to look there for them, while the heading
> only says APCI and APM.  I guess that the heading is too restrictive.

Yes, you're right, let's just kill the parentheses.

> 2.  APM and ACPI aren't usable together, right?  so should the
> Kconfig file prevent both of them from being enabled?

I'm not quite sure about this, though I believe that
ACPI at least in the CPU-enum-only configuration makes
sense even with APM enabled.

> 3.  The help text for Software Suspend (not part of this patch)
> really needs some help.  Would you address that or shall I?

Sure, it would be nice if you could fish out an entry from somewhere.

-- 
Tomas Szepe <szepe@pinerecords.com>

  reply	other threads:[~2003-07-27  2:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 20:02 [TRIVIAL] sanitize power management config menus Tomas Szepe
2003-07-27  2:46 ` Randy.Dunlap
2003-07-27  2:56   ` Tomas Szepe [this message]
2003-07-27  3:46     ` Randy.Dunlap
2003-07-27  5:02       ` Rahul Karnik
2003-07-27  6:57       ` Tomas Szepe
2003-07-27 11:13       ` Pavel Machek
2003-07-27 12:07         ` Tomas Szepe
2003-07-27  3:00   ` Linus Torvalds
2003-07-27  6:49   ` Matias Alejo Garcia

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=20030727025647.GB17724@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).