From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Len Brown <len.brown@intel.com>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
kernel list <linux-kernel@vger.kernel.org>,
Trivial patch monkey <trivial@kernel.org>
Subject: Re: [linux-pm] Re: Small pm documentation cleanups
Date: Thu, 07 Feb 2008 08:27:03 +1100 [thread overview]
Message-ID: <47AA2627.4030509@nigel.suspend2.net> (raw)
In-Reply-To: <20080205182712.GA9483@elf.ucw.cz>
Hi again.
Pavel Machek wrote:
> Hi!
>
>>> On Tuesday, 5 of February 2008, Pavel Machek wrote:
>>>> Small documentation fixes/additions that accumulated in my tree.
>>>>
>>>> Signed-off-by: Pavel Machek <pavel@suse.cz>
>>> Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
>>>
> ...
>>>> 0
>>>> acpi_sleep= [HW,ACPI] Sleep options
>>>> - Format: { s3_bios, s3_mode }
>>>> - See Documentation/power/video.txt
>>>> + Format: { s3_bios, s3_mode, s3_beep }
>>>> + See Documentation/power/video.txt for s3_bios and s3_mode.
>>>> + s3_beep is for debugging; it beeps on PC speaker as soon as
>>>> + kernel's real-mode entry point is called.
>> s/kernel's/the kernel's/
>
> Thanks for comments, I applied them.
You're welcome. Sorry for replying again, but I just noticed another one
in the line above - it should be something like "it makes the PC's
speaker beep as soon as" ('on PC speaker' isn't right).
Sorry for not getting that last time.
Nigel
next prev parent reply other threads:[~2008-02-06 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 23:47 Small pm documentation cleanups Pavel Machek
2008-02-05 1:24 ` Rafael J. Wysocki
2008-02-05 5:34 ` [linux-pm] " Nigel Cunningham
2008-02-05 18:27 ` Pavel Machek
2008-02-05 21:27 ` Jesper Juhl
2008-02-06 21:27 ` Nigel Cunningham [this message]
2008-02-06 21:31 ` Pavel Machek
2008-02-07 6:28 ` Len Brown
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=47AA2627.4030509@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=trivial@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