| 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
| ||
|
Date: Sat, 24 Mar 2018 01:26:30 +0100
From: Valentin Vidic <Valentin.Vidic@...Net.hr>
To: Stefani Seibold <stefani@...bold.net>
Cc: Mauro Carvalho Chehab <mchehab@...nel.org>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Jiri Kosina <jkosina@...e.cz>, Sean Young <sean@...s.org>,
linux-kernel@...r.kernel.org,
Valentin Vidic <Valentin.Vidic@...Net.hr>
Subject: [PATCH] kfifo: fix comment
Cleanup unusual formatting in the note about locking.
Signed-off-by: Valentin Vidic <Valentin.Vidic@...Net.hr>
---
include/linux/kfifo.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/kfifo.h b/include/linux/kfifo.h
index e251533a5939..89fc8dc7bf38 100644
--- a/include/linux/kfifo.h
+++ b/include/linux/kfifo.h
@@ -41,11 +41,11 @@
*/
/*
- * Note about locking : There is no locking required until only * one reader
- * and one writer is using the fifo and no kfifo_reset() will be * called
- * kfifo_reset_out() can be safely used, until it will be only called
+ * Note about locking: There is no locking required until only one reader
+ * and one writer is using the fifo and no kfifo_reset() will be called.
+ * kfifo_reset_out() can be safely used, until it will be only called
* in the reader thread.
- * For multiple writer and one reader there is only a need to lock the writer.
+ * For multiple writer and one reader there is only a need to lock the writer.
* And vice versa for only one writer and multiple reader there is only a need
* to lock the reader.
*/
--
2.16.2
Powered by blists - more mailing lists