From: SeongJae Park <sj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: SeongJae Park <sj@kernel.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] build_bug.h: correct function parameters names in kernel-doc
Date: Mon, 2 Mar 2026 18:15:31 -0800 [thread overview]
Message-ID: <20260303021532.119606-1-sj@kernel.org> (raw)
In-Reply-To: <20260302005144.3467019-1-rdunlap@infradead.org>
On Sun, 1 Mar 2026 16:51:44 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
> Use the correct function (or macro) names to avoid kernel-doc
> warnings:
>
> Warning: include/linux/build_bug.h:38 function parameter 'cond' not
> described in 'BUILD_BUG_ON_MSG'
> Warning: include/linux/build_bug.h:38 function parameter 'msg' not
> described in 'BUILD_BUG_ON_MSG'
> Warning: include/linux/build_bug.h:76 function parameter 'expr' not
> described in 'static_assert'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: SeongJae Park <sj@kernel.org>
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-03-03 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 0:51 [PATCH] build_bug.h: correct function parameters names in kernel-doc Randy Dunlap
2026-03-03 2:15 ` SeongJae Park [this message]
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=20260303021532.119606-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.