public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
	Andy Whitcroft <apw@canonical.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Fabian Frederick <fabf@skynet.be>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend] checkpatch: Replace __init_refok by __refconst and __refdata
Date: Mon, 17 Jul 2017 08:01:38 -0700	[thread overview]
Message-ID: <1500303698.25934.4.camel@perches.com> (raw)
In-Reply-To: <1500298924-13694-1-git-send-email-geert+renesas@glider.be>

On Mon, 2017-07-17 at 15:42 +0200, Geert Uytterhoeven wrote:
> As of commit bd721ea73e1f9655 ("treewide: replace obsolete _refok by
> __ref"), __init_refok no longer exists, so it can be removed.
> While at it, add the modern variants that were still missing.

Maybe nicer to add some phrase like "Update sparse keywords"
in the patch title

> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
>  scripts/checkpatch.pl | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 2287a0bca863bf57..b88740bfe9d14e41 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -343,9 +343,10 @@ our $Sparse	= qr{
>  			__force|
>  			__iomem|
>  			__must_check|
> -			__init_refok|
>  			__kprobes|
>  			__ref|
> +			__refconst|
> +			__refdata|
>  			__rcu|
>  			__private
>  		}x;

Anyway:

Acked-by: Joe Perches <joe@perches.com>

  reply	other threads:[~2017-07-17 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 13:42 [PATCH resend] checkpatch: Replace __init_refok by __refconst and __refdata Geert Uytterhoeven
2017-07-17 15:01 ` Joe Perches [this message]
2017-07-18 12:20   ` Geert Uytterhoeven

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=1500303698.25934.4.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=fabf@skynet.be \
    --cc=geert+renesas@glider.be \
    --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