include/linux/kfifo.h: fix comment
Clean up unusual formatting in the note about locking. Link: http://lkml.kernel.org/r/20180324002630.13046-1-Valentin.Vidic@CARNet.hr Signed-off-by: Valentin Vidic <Valentin.Vidic@CARNet.hr> Cc: Stefani Seibold <stefani@seibold.net> Cc: Mauro Carvalho Chehab <mchehab@kernel.org> Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr> Cc: Jiri Kosina <jkosina@suse.cz> Cc: Sean Young <sean@mess.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
a61fc2cbdf
commit
de99626c2e
|
@ -41,11 +41,11 @@
|
||||||
*/
|
*/
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Note about locking : There is no locking required until only * one reader
|
* 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
|
* 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
|
* kfifo_reset_out() can be safely used, until it will be only called
|
||||||
* in the reader thread.
|
* 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
|
* And vice versa for only one writer and multiple reader there is only a need
|
||||||
* to lock the reader.
|
* to lock the reader.
|
||||||
*/
|
*/
|
||||||
|
|
Loading…
Reference in New Issue