lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 23 Mar 2017 21:47:59 +0000
From:   "Zhang, Shile (Nokia - CN/Hangzhou)" <shile.zhang@...ia.com>
To:     Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3] hangcheck-timer: Fix typo in comment

>Fix the typo "alloted" -> "allotted" in comment.
>
>Signed-off-by: Shile Zhang <shile.zhang@...ia.com>
>---
> drivers/char/hangcheck-timer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/char/hangcheck-timer.c b/drivers/char/hangcheck-timer.c
>index 4f33737..5406b90 100644
>--- a/drivers/char/hangcheck-timer.c
>+++ b/drivers/char/hangcheck-timer.c
>@@ -32,7 +32,7 @@
>  * timer and 180 seconds for the margin of error.  IOW, a timer is set
>  * for 60 seconds.  When the timer fires, the callback checks the
>  * actual duration that the timer waited.  If the duration exceeds the
>- * alloted time and margin (here 60 + 180, or 240 seconds), the machine
>+ * allotted time and margin (here 60 + 180, or 240 seconds), the machine
>  * is restarted.  A healthy machine will have the duration match the
>  * expected timeout very closely.
>  */
>--
>2.6.2

Hi Greg,

Sorry for trouble!
Dose this format is OK in this version?
Thanks!

BR, Shile

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ