From: Kit Dallege <xaum.io@gmail.com>
To: Chris Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org,
Kit Dallege <xaum.io@gmail.com>, Claude <noreply@anthropic.com>
Subject: [PATCH 5/9] compiler.h: add missing kernel-doc for data_race() @expr parameter
Date: Sun, 15 Mar 2026 16:34:53 +0100 [thread overview]
Message-ID: <20260315153453.48535-1-xaum.io@gmail.com> (raw)
Document the @expr parameter for the data_race() macro that was missing
from the kernel-doc comment.
Assisted-by: Claude <noreply@anthropic.com>
Signed-off-by: Kit Dallege <xaum.io@gmail.com>
---
include/linux/compiler.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/compiler.h b/include/linux/compiler.h
index af16624b29fd..4ae001bb6442 100644
--- a/include/linux/compiler.h
+++ b/include/linux/compiler.h
@@ -171,6 +171,7 @@ void ftrace_likely_update(struct ftrace_likely_data *f, int val,
/**
* data_race - mark an expression as containing intentional data races
+ * @expr: the expression to execute with data race checking disabled
*
* This data_race() macro is useful for situations in which data races
* should be forgiven. One example is diagnostic code that accesses
--
2.53.0
reply other threads:[~2026-03-15 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260315153453.48535-1-xaum.io@gmail.com \
--to=xaum.io@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=noreply@anthropic.com \
--cc=sparse@chrisli.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