[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231017053703.11312-1-clh960524@gmail.com>
Date: Tue, 17 Oct 2023 13:37:03 +0800
From: Cuda-Chen <clh960524@...il.com>
To: peterz@...radead.org
Cc: mingo@...hat.com, will@...nel.org, longman@...hat.com,
boqun.feng@...il.com, linux-kernel@...r.kernel.org,
Cuda-Chen <clh960524@...il.com>
Subject: [PATCH] locking/seqlock: Fix grammer error
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@...il.com>
---
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 e9bd2f65d..734d9c598 100644
--- a/include/linux/seqlock.h
+++ b/include/linux/seqlock.h
@@ -574,7 +574,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;
--
2.34.1
Powered by blists - more mailing lists