From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] Adding ignored attribute optimize
Date: Thu, 29 Jun 2017 09:04:38 +0200 [thread overview]
Message-ID: <20170629070437.o6j2bkv6wdbcknwa@ltop.local> (raw)
In-Reply-To: <CANeU7QnNNL1u3BxhWLebFqzn+9Y7hHKABDo_mkEqfwF+VO963Q@mail.gmail.com>
On Tue, Jun 27, 2017 at 10:21:43AM -0700, Christopher Li wrote:
> I notice this unknow attribute "__optimize__"when I am looking
> sparse checking result on the recent kernel compile.
There is also a long time 'require_context' in drivers/block/drbd,/
a failed attempt to fix or extend sparse's handling of lock context.
Why is it still there after all those years, I have no idea.
Anyway, my position about these unknown attributes is still the same
of course: we should simply ignore them instead of annoying people
with useless warnings.
-- Luc
next prev parent reply other threads:[~2017-06-29 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 17:21 [PATCH] Adding ignored attribute optimize Christopher Li
2017-06-29 7:04 ` Luc Van Oostenryck [this message]
2017-06-29 21:46 ` Christopher Li
2017-07-01 9:24 ` Luc Van Oostenryck
2017-07-01 22:21 ` Christopher Li
2017-07-02 19:58 ` Luc Van Oostenryck
2017-07-03 18:23 ` Christopher Li
2017-07-03 20:41 ` Luc Van Oostenryck
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=20170629070437.o6j2bkv6wdbcknwa@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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