The following commit has been merged into the locking/core branch of tip: Commit-ID: 184fdf9fc7ae6ae7155768faa48fc609d1a24b7e Gitweb: https://git.kernel.org/tip/184fdf9fc7ae6ae7155768faa48fc609d1a24b7e Author: Cuda-Chen <clh960524@xxxxxxxxx> AuthorDate: Tue, 17 Oct 2023 13:37:03 +08:00 Committer: Ingo Molnar <mingo@xxxxxxxxxx> CommitterDate: Tue, 17 Oct 2023 13:28:12 +02:00 locking/seqlock: Fix grammar in comment The "neither writes before and after ..." for the description of do_write_seqcount_end() should be "neither writes before nor after". Signed-off-by: Cuda-Chen <clh960524@xxxxxxxxx> Signed-off-by: Ingo Molnar <mingo@xxxxxxxxxx> Link: https://lore.kernel.org/r/20231017053703.11312-1-clh960524@xxxxxxxxx --- include/linux/seqlock.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/seqlock.h b/include/linux/seqlock.h index 80f21d2..e92f9d5 100644 --- a/include/linux/seqlock.h +++ b/include/linux/seqlock.h @@ -584,7 +584,7 @@ static inline void do_write_seqcount_end(seqcount_t *s) * via WRITE_ONCE): a) to ensure the writes become visible to other threads * atomically, avoiding compiler optimizations; b) to document which writes are * meant to propagate to the reader critical section. This is necessary because - * neither writes before and after the barrier are enclosed in a seq-writer + * neither writes before nor after the barrier are enclosed in a seq-writer * critical section that would ensure readers are aware of ongoing writes:: * * seqcount_t seq;
|