lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 18 Feb 2017 02:19:57 +0100
From:   "Rafael J. Wysocki" <>
To:     Geert Uytterhoeven <>
Cc:     Jiri Kosina <>,,
Subject: Re: [PATCH trivial 4/4] PM / Documentation: Spelling s/wrtie/write/

On Friday, February 17, 2017 04:36:39 PM Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <>
> Cc: Rafael J. Wysocki <>
> Cc:
> ---
>  Documentation/power/states.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/Documentation/power/states.txt b/Documentation/power/states.txt
> index 008ecb588317bc1d..bc4548245a243134 100644
> --- a/Documentation/power/states.txt
> +++ b/Documentation/power/states.txt
> @@ -25,7 +25,7 @@ to be used subsequently to change to the one represented by that string.
>  Consequently, there are two ways to cause the system to go into the
>  Suspend-To-Idle sleep state.  The first one is to write "freeze" directly to
>  /sys/power/state.  The second one is to write "s2idle" to /sys/power/mem_sleep
> -and then to wrtie "mem" to /sys/power/state.  Similarly, there are two ways
> +and then to write "mem" to /sys/power/state.  Similarly, there are two ways
>  to cause the system to go into the Power-On Suspend sleep state (the strings to
>  write to the control files in that case are "standby" or "shallow" and "mem",
>  respectively) if that state is supported by the platform.  In turn, there is



Powered by blists - more mailing lists