mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Andy Whitcroft <apw@canonical.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Joe Perches <joe@perches.com>,
	Patrick Pannuto <ppannuto@codeaurora.org>,
	Wolfram Sang <w.sang@pengutronix.de>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: teach checkpatch about rcu
Date: Thu, 18 Nov 2010 18:15:47 +0100	[thread overview]
Message-ID: <1290100547.2781.206.camel@edumazet-laptop> (raw)
In-Reply-To: <20101118170515.GA14005@redhat.com>

Le jeudi 18 novembre 2010 à 19:05 +0200, Michael S. Tsirkin a écrit :
> I got this:
> +       struct kvm_kernel_irq_routing_entry __rcu *irq_entry;
> which is because checkpatch does not know about __rcu.
> So here's a patch to teach it about that tag.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>  scripts/checkpatch.pl |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 2039acd..1b11c8e 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -143,6 +143,7 @@ our $Sparse	= qr{
>  			__must_check|
>  			__init_refok|
>  			__kprobes|
> +			__rcu|
>  			__ref
>  		}x;
>  


Hmm, why __percpu is in $Attribute, and __rcu in $Sparse ?




  reply	other threads:[~2010-11-18 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 17:05 Michael S. Tsirkin
2010-11-18 17:15 ` Eric Dumazet [this message]
2010-11-21  8:31   ` Michael S. Tsirkin

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=1290100547.2781.206.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=ppannuto@codeaurora.org \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=w.sang@pengutronix.de \
    /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®