From: Randy Dunlap <rdunlap@xenotime.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Kumar Appaiah <a.kumar@alumni.iitm.ac.in>,
Matthew Garrett <mjg@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thinkpad-acpi: minor grammatical fixes to documentation
Date: Sat, 27 Aug 2011 15:16:57 -0700 [thread overview]
Message-ID: <20110827151657.0641a353.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110825030654.GA6074@khazad-dum.debian.net>
On Thu, 25 Aug 2011 00:06:54 -0300 Henrique de Moraes Holschuh wrote:
> On Tue, 23 Aug 2011, Kumar Appaiah wrote:
> > This commit adds minor grammatical fixes to the description of the
> > keys in the thinkpad-acpi documentation.
> >
> > Signed-off-by: Kumar Appaiah <a.kumar@alumni.iitm.ac.in>
> Acked-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Applied, thanks.
> > ---
> > Documentation/laptops/thinkpad-acpi.txt | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/laptops/thinkpad-acpi.txt b/Documentation/laptops/thinkpad-acpi.txt
> > index 6181548..b73dcea 100644
> > --- a/Documentation/laptops/thinkpad-acpi.txt
> > +++ b/Documentation/laptops/thinkpad-acpi.txt
> > @@ -411,9 +411,9 @@ event code Key Notes
> >
> > 0x1004 0x03 FN+F4 Sleep button (ACPI sleep button
> > semantics, i.e. sleep-to-RAM).
> > - It is always generate some kind
> > + It always generates some kind
> > of event, either the hot key
> > - event or a ACPI sleep button
> > + event or an ACPI sleep button
> > event. The firmware may
> > refuse to generate further FN+F4
> > key presses until a S3 or S4 ACPI
>
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-08-27 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 15:11 Kumar Appaiah
2011-08-25 3:06 ` Henrique de Moraes Holschuh
2011-08-27 22:16 ` Randy Dunlap [this message]
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=20110827151657.0641a353.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=a.kumar@alumni.iitm.ac.in \
--cc=hmh@hmh.eng.br \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
/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
all inboxes | Powered by JetHome®