[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1341307645-15135-1-git-send-email-oskar@scara.com>
Date: 3 Jul 2012 09:27:24 +0000
From: "Oskar Schirmer" <oskar@...ra.com>
To: "Rob Landley" <rob@...dley.net>
Cc: linux-kernel@...r.kernel.org,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Oskar Schirmer" <oskar@...ra.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"David Brownell" <david-b@...bell.net>,
"Alan Stern" <stern@...land.harvard.edu>
Subject: [PATCH 1/2] Documentation: fix typos in power management description
Just two missing characters.
Signed-off-by: Oskar Schirmer <oskar@...ra.com>
Cc: Rafael J. Wysocki <rjw@...k.pl>
Cc: David Brownell <david-b@...bell.net>
Cc: Alan Stern <stern@...land.harvard.edu>
---
Documentation/power/devices.txt | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/Documentation/power/devices.txt b/Documentation/power/devices.txt
index 872815c..504dfe4 100644
--- a/Documentation/power/devices.txt
+++ b/Documentation/power/devices.txt
@@ -583,9 +583,10 @@ for the given device during all power transitions, instead of the respective
subsystem-level callbacks. Specifically, if a device's pm_domain pointer is
not NULL, the ->suspend() callback from the object pointed to by it will be
executed instead of its subsystem's (e.g. bus type's) ->suspend() callback and
-anlogously for all of the remaining callbacks. In other words, power management
-domain callbacks, if defined for the given device, always take precedence over
-the callbacks provided by the device's subsystem (e.g. bus type).
+analogously for all of the remaining callbacks. In other words, power
+management domain callbacks, if defined for the given device, always take
+precedence over the callbacks provided by the device's subsystem (e.g. bus
+type).
The support for device power management domains is only relevant to platforms
needing to use the same device driver power management callbacks in many
@@ -598,7 +599,7 @@ it into account in any way.
Device Low Power (suspend) States
---------------------------------
Device low-power states aren't standard. One device might only handle
-"on" and "off, while another might support a dozen different versions of
+"on" and "off", while another might support a dozen different versions of
"on" (how many engines are active?), plus a state that gets back to "on"
faster than from a full "off".
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists