From: Christopher Li <sparse@chrisli.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: sparse: add noclone as an ignored attribute
Date: Thu, 21 Feb 2013 15:35:58 -0800 [thread overview]
Message-ID: <CANeU7Qk+5RMN--w_BQpUoX5yh_fkdfme7AxVpm3HXVyZX_inJQ@mail.gmail.com> (raw)
In-Reply-To: <51184E28.40909@infradead.org>
On Sun, Feb 10, 2013 at 5:49 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Add attribute "noclone" or "__noclone" or "__noclone__" as an
> ignored attribute. Fixes this sparse warning:
>
> arch/x86/kvm/vmx.c:6268:13: error: attribute '__noclone__': unknown attribute
The change looks good. Can you add a test case for the noclone attribute
in the validations directory? I am happy to apply it.
Chris
next prev parent reply other threads:[~2013-02-21 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 1:49 sparse: add noclone as an ignored attribute Randy Dunlap
2013-02-21 23:35 ` Christopher Li [this message]
2013-02-22 0:20 ` sparse patch v2: " Randy Dunlap
2013-02-22 0:56 ` Christopher Li
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=CANeU7Qk+5RMN--w_BQpUoX5yh_fkdfme7AxVpm3HXVyZX_inJQ@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).