From: Greg Kroah-Hartman <gregkh@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Henrik Austad <henrik@austad.us>,
Randy Dunlap <randy.dunlap@oracle.com>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: [PATCH 2/5] Doc/sysfs-rules: Swap the order of the words so the sentence makes more sense
Date: Fri, 8 May 2009 20:25:56 -0700 [thread overview]
Message-ID: <1241839559-9157-2-git-send-email-gregkh@suse.de> (raw)
In-Reply-To: <20090509032432.GA9000@kroah.com>
From: Henrik Austad <henrik@austad.us>
Signed-off-by: Henrik Austad <henrik@austad.us>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
Documentation/sysfs-rules.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/sysfs-rules.txt b/Documentation/sysfs-rules.txt
index 6049a2a..5d8bc2c 100644
--- a/Documentation/sysfs-rules.txt
+++ b/Documentation/sysfs-rules.txt
@@ -113,7 +113,7 @@ versions of the sysfs interface.
"devices" directory at /sys/subsystem/<name>/devices.
If /sys/subsystem exists, /sys/bus, /sys/class and /sys/block can be
- ignored. If it does not exist, you have always to scan all three
+ ignored. If it does not exist, you always have to scan all three
places, as the kernel is free to move a subsystem from one place to
the other, as long as the devices are still reachable by the same
subsystem name.
--
1.6.3
next prev parent reply other threads:[~2009-05-09 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 3:24 [GIT PATCH] USB fixes for 2.6.30-rc4 Greg KH
2009-05-09 3:25 ` [PATCH 1/5] Driver core: platform: fix kernel-doc warnings Greg Kroah-Hartman
2009-05-09 3:25 ` Greg Kroah-Hartman [this message]
2009-05-09 3:25 ` [PATCH 3/5] Remove old PRINTK_DEBUG config item Greg Kroah-Hartman
2009-05-09 3:25 ` [PATCH 4/5] Revert driver core: fix passing platform_data Greg Kroah-Hartman
2009-05-09 3:25 ` [PATCH 5/5] Revert driver core: move platform_data into platform_device Greg Kroah-Hartman
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=1241839559-9157-2-git-send-email-gregkh@suse.de \
--to=gregkh@suse.de \
--cc=henrik@austad.us \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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