From: Joe Perches <joe@perches.com>
To: Paul Walmsley <pjw@kernel.org>,
apw@canonical.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: Nam Cao <namcao@linutronix.de>, Jisheng Zhang <jszhang@kernel.org>
Subject: Re: [PATCH] checkpatch: add NOKPROBE_SYMBOL to the whitelist of lines that can occur immediately after functions
Date: Thu, 06 Aug 2026 18:17:44 -0700 [thread overview]
Message-ID: <3dccf110a71f2459dcbc44684b6ebbbff16986e4.camel@perches.com> (raw)
In-Reply-To: <130be7db-6098-86a4-60fe-0c1a5d9e30ba@kernel.org>
On Thu, 2026-08-06 at 19:00 -0600, Paul Walmsley wrote:
> It's customary for NOKPROBE_SYMBOL() macro usage to appear immedately
immediate typo.
Andrew can you please fix it when applying?
Anyway, this is completely sensible, thanks.
Acked-by: Joe Perches <joe@perches.com>
> after a function's final closing brace, but checkpatch doesn't know
> that yet. As a result, checkpatch --strict incorrectly flags this
> common kernel pattern, e.g.,
>
> CHECK: Please use a blank line after function/struct/union/enum declarations
> 33: FILE: arch/riscv/kernel/traps.c:273:
> }
> +NOKPROBE_SYMBOL(probe_single_step_handler);
>
> Fix by adding NOKPROBE_SYMBOL to the whitelist of patterns that are
> cleared to appear immediately after functions.
>
> Cc: Nam Cao <[namcao@linutronix.de](mailto:namcao@linutronix.de)>
> Cc: Jisheng Zhang <[jszhang@kernel.org](mailto:jszhang@kernel.org)>
> Signed-off-by: Paul Walmsley <[pjw@kernel.org](mailto:pjw@kernel.org)>
> ---
> scripts/checkpatch.pl | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 2b7a42bbdd94..f8a57ed71f34 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -4148,6 +4148,7 @@ sub process {
> $line =~ /^\+[a-z_]*init/ ||
> $line =~ /^\+\s*(?:static\s+)?[A-Z_]*ATTR/ ||
> $line =~ /^\+\s*DECLARE/ ||
> + $line =~ /^\+\s*NOKPROBE_SYMBOL/ ||
> $line =~ /^\+\s*builtin_[\w_]*driver/ ||
> $line =~ /^\+\s*__setup/)) {
> if (CHK("LINE_SPACING",
>
> ```
next prev parent reply other threads:[~2026-08-07 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 1:00 Paul Walmsley
2026-08-07 1:17 ` Joe Perches [this message]
2026-08-10 16:57 ` Petr Vorel
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=3dccf110a71f2459dcbc44684b6ebbbff16986e4.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=pjw@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®