diff options
author | John Ogness <[email protected]> | 2024-02-07 14:46:57 +0106 |
---|---|---|
committer | Petr Mladek <[email protected]> | 2024-02-07 17:23:18 +0100 |
commit | 584528d621459d1a5c31da7a591218ad3bb96d6c (patch) | |
tree | f1a953e7b1024ff242d32f078f7c3af94919e24d /lib/test_fortify/write_overflow-strscpy.c | |
parent | 36652d0f3bf34899e82d31a5fa9e2bdd02fd6381 (diff) |
printk: ringbuffer: Cleanup reader terminology
With the lockless ringbuffer, it is allowed that multiple
CPUs/contexts write simultaneously into the buffer. This creates
an ambiguity as some writers will finalize sooner.
The documentation for the prb_read functions is not clear as it
refers to "not yet written" and "no data available". Clarify the
return values and language to be in terms of the reader: records
available for reading.
Signed-off-by: John Ogness <[email protected]>
Reviewed-by: Petr Mladek <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Petr Mladek <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strscpy.c')
0 files changed, 0 insertions, 0 deletions