summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRandy Dunlap <rdunlap@infradead.org>2023-01-27 07:39:51 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2023-01-30 19:13:20 +0100
commit71bc571c64c13734c69c854e97fb97ac7bf7b54a (patch)
tree8704214927ea5bc8ab488b74566d2022a94b99a0
parentLinux 6.2-rc6 (diff)
downloadlinux-71bc571c64c13734c69c854e97fb97ac7bf7b54a.tar.xz
linux-71bc571c64c13734c69c854e97fb97ac7bf7b54a.zip
Documentation: power: correct spelling
Correct spelling problems for Documentation/power/ as reported by codespell. Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
-rw-r--r--Documentation/power/suspend-and-interrupts.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/power/suspend-and-interrupts.rst b/Documentation/power/suspend-and-interrupts.rst
index 4cda6617709a..dfbace2f4600 100644
--- a/Documentation/power/suspend-and-interrupts.rst
+++ b/Documentation/power/suspend-and-interrupts.rst
@@ -67,7 +67,7 @@ That may involve turning on a special signal handling logic within the platform
during system sleep so as to trigger a system wakeup when needed. For example,
the platform may include a dedicated interrupt controller used specifically for
handling system wakeup events. Then, if a given interrupt line is supposed to
-wake up the system from sleep sates, the corresponding input of that interrupt
+wake up the system from sleep states, the corresponding input of that interrupt
controller needs to be enabled to receive signals from the line in question.
After wakeup, it generally is better to disable that input to prevent the
dedicated controller from triggering interrupts unnecessarily.