From: Mark Brown <broonie@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Matthias Kaehlcke <mka@chromium.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linux-mm@kvack.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [patch] compiler, clang: suppress warning for unused static inline functions
Date: Wed, 31 May 2017 19:26:13 +0100 [thread overview]
Message-ID: <20170531182613.sagvoniu53nehath@sirena.org.uk> (raw)
In-Reply-To: <CAD=FV=Xi7NjDjsdwGP=GGS9p=uUpqZa7S=irNOFmhfD1F3kWZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On Wed, May 31, 2017 at 08:53:40AM -0700, Doug Anderson wrote:
> It is certainly possible that something like this could be done (I
> think Coverity works something like this), but I'm not sure there are
> any volunteers. Doing this would require a person to setup and
> monitor a clang builder and then setup a list of false positives. For
> each new warning this person would need to analyze the warning and
> either send a patch or add it to the list of false positives.
It also means setting up some mechanism for distributing the blacklist
or that that every individual person or group doing clang stuff would
need to replicate the work.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-05-31 18:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 21:01 David Rientjes
2017-05-24 21:22 ` Matthias Kaehlcke
2017-05-24 21:32 ` Andrew Morton
2017-05-24 23:28 ` Doug Anderson
2017-05-31 0:10 ` David Rientjes
2017-05-31 1:53 ` Matthias Kaehlcke
2017-05-31 15:53 ` Doug Anderson
2017-05-31 18:26 ` Mark Brown [this message]
2017-05-31 21:45 ` David Rientjes
2017-05-31 22:31 ` Doug Anderson
2017-06-01 0:01 ` Matthias Kaehlcke
2017-05-25 5:52 ` Ingo Molnar
2017-05-25 16:14 ` Matthias Kaehlcke
2017-05-25 16:48 ` Joe Perches
2017-05-25 17:49 ` Matthias Kaehlcke
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=20170531182613.sagvoniu53nehath@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/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