From: Randy Dunlap <rdunlap@xenotime.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kumar Appaiah <a.kumar@alumni.iitm.ac.in>
Subject: [PATCH 2/8] Documentation: thinkpad-acpi grammo fixes
Date: Fri, 04 Nov 2011 11:22:09 -0700 [thread overview]
Message-ID: <4EB42D51.50100@xenotime.net> (raw)
In-Reply-To: <4EB423D8.9030102@xenotime.net>
From: Kumar Appaiah <a.kumar@alumni.iitm.ac.in>
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>
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
Documentation/laptops/thinkpad-acpi.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- lnx1104.orig/Documentation/laptops/thinkpad-acpi.txt
+++ lnx1104/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
next parent reply other threads:[~2011-11-04 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EB423D8.9030102@xenotime.net>
2011-11-04 18:22 ` Randy Dunlap [this message]
2011-11-04 18:22 ` [PATCH 3/8] Documentation: fix inotify source file paths Randy Dunlap
2011-11-04 18:22 ` [PATCH 4/8] Documentation: update CodingStyle use of braces Randy Dunlap
2011-11-04 18:22 ` [PATCH 5/8] Documentation: HFS is orphaned Randy Dunlap
2011-11-04 18:22 ` [PATCH 6/8] Documentation: Computone ip2 " Randy Dunlap
2011-11-04 18:22 ` [PATCH 7/8] Documentation: fix leds-class.txt duplicated word Randy Dunlap
2011-11-04 18:22 ` [PATCH 8/8] Documentation: drop as block elevator reference in switching-sched.txt Randy Dunlap
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=4EB42D51.50100@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=a.kumar@alumni.iitm.ac.in \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.