From: Josh Triplett <josh@joshtriplett.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: linux-sparse@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Lance Richardson <lrichard@redhat.com>,
Ramsay Jones <ramsay@ramsayjones.plus.com>,
Randy Dunlap <rdunlap@infradead.org>,
Rui Teng <rui.teng@linux.vnet.ibm.com>,
Christopher Li <sparse@chrisli.org>
Subject: Re: [RFC PATCH 0/2] drop the concept of 'known-but-ignored' attributes
Date: Thu, 15 Feb 2018 07:57:25 -0800 [thread overview]
Message-ID: <20180215155724.GB1882@localhost> (raw)
In-Reply-To: <20180213232109.20933-1-luc.vanoostenryck@gmail.com>
On Wed, Feb 14, 2018 at 12:21:07AM +0100, Luc Van Oostenryck wrote:
> The goal of this series is to drop the concept of
> 'known-but-ignored' attributes which, for a semantic
> checker like sparse, adds absolutely no added value
> but bring endless annoyances.
I absolutely agree that these have been annoying. However, they've also
been useful in the past to identify new flags used in the kernel and
other projects that we may need to actually act on, rather than just
ignore.
next prev parent reply other threads:[~2018-02-15 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 23:21 [RFC PATCH 0/2] drop the concept of 'known-but-ignored' attributes Luc Van Oostenryck
2018-02-13 23:21 ` [RFC PATCH 1/2] By default disable the warning flag '-Wunknown-attribute' Luc Van Oostenryck
2018-02-13 23:21 ` [RFC PATCH 2/2] drop the concept of 'known-but-ignored' attributes Luc Van Oostenryck
2018-02-15 15:57 ` Josh Triplett [this message]
2018-02-15 17:33 ` [RFC PATCH 0/2] " Linus Torvalds
2018-02-15 17:54 ` Josh Triplett
2018-02-15 20:03 ` Luc Van Oostenryck
2018-02-15 19:53 ` Luc Van Oostenryck
2018-02-15 20:06 ` 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=20180215155724.GB1882@localhost \
--to=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=lrichard@redhat.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=ramsay@ramsayjones.plus.com \
--cc=rdunlap@infradead.org \
--cc=rui.teng@linux.vnet.ibm.com \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.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).