From: carlos.bilbao@kernel.org
To: corbet@lwn.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: bilbao@vt.edu, Carlos Bilbao <carlos.bilbao@kernel.org>
Subject: [PATCH] docs/core-api: Fix circular buffer examples
Date: Sun, 20 Jul 2025 11:02:43 -0500 [thread overview]
Message-ID: <20250720160243.149595-1-carlos.bilbao@kernel.org> (raw)
From: Carlos Bilbao <carlos.bilbao@kernel.org>
Fix circular buffer usage in producer/consumer examples in
circular-buffers.rst. They incorrectly access items using buffer[head] and
buffer[tail], as if buffer was a flat array; but the examples also use
buffer->head and buffer->tail, so it's a struct. Use buffer->vals[head] and
buffer->vals[tail] instead to match the intended layout.
Signed-off-by: Carlos Bilbao <carlos.bilbao@kernel.org>
---
Documentation/core-api/circular-buffers.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/core-api/circular-buffers.rst b/Documentation/core-api/circular-buffers.rst
index 50966f66e398..b697915a2bd0 100644
--- a/Documentation/core-api/circular-buffers.rst
+++ b/Documentation/core-api/circular-buffers.rst
@@ -161,7 +161,7 @@ The producer will look something like this::
if (CIRC_SPACE(head, tail, buffer->size) >= 1) {
/* insert one item into the buffer */
- struct item *item = buffer[head];
+ struct item *item = buffer->vals[head];
produce_item(item);
@@ -203,7 +203,7 @@ The consumer will look something like this::
if (CIRC_CNT(head, tail, buffer->size) >= 1) {
/* extract one item from the buffer */
- struct item *item = buffer[tail];
+ struct item *item = buffer->vals[tail];
consume_item(item);
--
2.43.0
next reply other threads:[~2025-07-20 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 16:02 carlos.bilbao [this message]
2025-07-21 2:47 ` Akira Yokosawa
2025-07-23 20:47 ` Paul E. McKenney
2025-08-04 22:05 ` Carlos Bilbao
2025-08-06 17:19 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250720160243.149595-1-carlos.bilbao@kernel.org \
--to=carlos.bilbao@kernel.org \
--cc=bilbao@vt.edu \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®