From 2425b5168ca9c4969c8d6bda0a15dd61eb0d4698 Mon Sep 17 00:00:00 2001 From: Mateusz Guzik Date: Sun, 12 May 2019 07:13:25 +0000 Subject: [PATCH] seqc: fix sed-introduced typos (seqcuence -> sequence) Sponsored by: The FreeBSD Foundation --- sys/sys/seqc.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sys/sys/seqc.h b/sys/sys/seqc.h index 41da448ab4e5..9dd3ae7b262f 100644 --- a/sys/sys/seqc.h +++ b/sys/sys/seqc.h @@ -44,9 +44,9 @@ typedef uint32_t seqc_t; * seqc allows readers and writers to work with a consistent snapshot. Modifying * operations must be enclosed within a transaction delineated by * seqc_write_beg/seqc_write_end. The trick works by having the writer increment - * the seqcuence number twice, at the beginning and end of the transaction. - * The reader detects that the seqcuence number has not changed between its start - * and end, and that the seqcuence number is even, to validate consistency. + * the sequence number twice, at the beginning and end of the transaction. + * The reader detects that the sequence number has not changed between its start + * and end, and that the sequence number is even, to validate consistency. * * Some fencing (both hard fencing and compiler barriers) may be needed, * depending on the cpu. Modern AMD cpus provide strong enough guarantees to not