From: Pavel Machek <pavel@ucw.cz>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org,
Carlos Corbacho <carlos@strangeworlds.co.uk>,
Ray Lee <ray-lk@madrabbit.org>, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 7/8] ACPI: WMI: Improve Kconfig description
Date: Fri, 8 Feb 2008 23:09:06 +0100 [thread overview]
Message-ID: <20080208220906.GA1648@elf.ucw.cz> (raw)
In-Reply-To: <20b4514799ebcfb04b45537e90e421cb73fd0cc9.1202452053.git.len.brown@intel.com>
On Fri 2008-02-08 01:29:23, Len Brown wrote:
> From: Carlos Corbacho <carlos@strangeworlds.co.uk>
>
> As Pavel Machek has pointed out, the Kconfig entry for WMI is pretty
> non-descriptive.
>
> Rewrite it so that it explains what ACPI-WMI is, and why anyone
> would want to enable it.
>
> Many thanks to Ray Lee for ideas on this.
>
> Signed-off-by: Carlos Corbacho <carlos@strangeworlds.co.uk>
> CC: Pavel Machek <pavel@ucw.cz>
ACK... and thanks.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-02-08 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 6:29 ACPI patches for 2.6.25-rc0 (more) Len Brown
2008-02-08 6:29 ` [PATCH 1/8] ACPI: add newline to printk Len Brown
2008-02-08 6:29 ` [PATCH 2/8] ACPI: cpufreq: Print _PPC changes via cpufreq debug layer Len Brown
2008-02-08 6:29 ` [PATCH 3/8] ACPI: build WMI on X86 only Len Brown
2008-02-08 9:41 ` Carlos Corbacho
2008-02-08 6:29 ` [PATCH 4/8] intel_menlo: build " Len Brown
2008-02-08 6:29 ` [PATCH 5/8] ACPI: thermal: syntax, spelling, kernel-doc Len Brown
2008-02-08 6:29 ` [PATCH 6/8] ACPI: DMI: add Panasonic CF-52 and Thinpad X61 Len Brown
2008-02-08 6:29 ` [PATCH 7/8] ACPI: WMI: Improve Kconfig description Len Brown
2008-02-08 22:09 ` Pavel Machek [this message]
2008-02-08 6:29 ` [PATCH 8/8] acer-wmi, tc1100-wmi: select ACPI_WMI Len Brown
2008-02-08 9:37 ` Carlos Corbacho
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=20080208220906.GA1648@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=carlos@strangeworlds.co.uk \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=ray-lk@madrabbit.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