From: John Hubbard <jhubbard@nvidia.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc: Ofir Drang <ofir.drang@arm.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] checkpatch: add *_NOTIFIER_HEAD as var definition
Date: Mon, 19 Aug 2019 11:28:11 -0700 [thread overview]
Message-ID: <777c39df-bef3-e095-7299-80f55b50158a@nvidia.com> (raw)
In-Reply-To: <20190819122917.11896-1-gilad@benyossef.com>
On 8/19/19 5:29 AM, Gilad Ben-Yossef wrote:
> Add *_NOTIFIER_HEAD as variable definition to avoid code like this:
>
> ATOMIC_NOTIFIER_HEAD(foo);
> EXPORT_SYMBOL_GPL(foo);
>
> From triggering the the following warning:
> WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable
>
> Signed-off-by: Gilad Ben-Yossef <gilad@benyossef.com>
> Cc: John Hubbard <jhubbard@nvidia.com>
> ---
>
> Changes from v1:
> - Fixed misposition of braces.
> - Tested on 1k last commits from Linux tree.
Hi Gilad,
I re-ran this updated patch, on my local patches that were showing the problem,
and it is All Better Now. :) So you can add:
Tested-by: John Hubbard <jhubbard@nvidia.com>
thanks,
--
John Hubbard
NVIDIA
>
> scripts/checkpatch.pl | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 93a7edfe0f05..8bc0e753a329 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -3864,6 +3864,7 @@ sub process {
> ^.DEFINE_$Ident\(\Q$name\E\)|
> ^.DECLARE_$Ident\(\Q$name\E\)|
> ^.LIST_HEAD\(\Q$name\E\)|
> + ^.${Ident}_NOTIFIER_HEAD\(\Q$name\E\)|
> ^.(?:$Storage\s+)?$Type\s*\(\s*\*\s*\Q$name\E\s*\)\s*\(|
> \b\Q$name\E(?:\s+$Attribute)*\s*(?:;|=|\[|\()
> )/x) {
>
next prev parent reply other threads:[~2019-08-19 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 12:29 Gilad Ben-Yossef
2019-08-19 18:28 ` John Hubbard [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-04 10:44 Gilad Ben-Yossef
2019-07-04 18:55 ` Joe Perches
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=777c39df-bef3-e095-7299-80f55b50158a@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=apw@canonical.com \
--cc=gilad@benyossef.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ofir.drang@arm.com \
/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
Powered by JetHome