From: Joe Perches <joe@perches.com>
To: Matthias Kaehlcke <mka@chromium.org>, Ingo Molnar <mingo@kernel.org>
Cc: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.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,
Douglas Anderson <dianders@chromium.org>,
Mark Brown <broonie@kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [patch] compiler, clang: suppress warning for unused static inline functions
Date: Thu, 25 May 2017 09:48:53 -0700 [thread overview]
Message-ID: <1495730933.29207.6.camel@perches.com> (raw)
In-Reply-To: <20170525161406.GT141096@google.com>
On Thu, 2017-05-25 at 09:14 -0700, Matthias Kaehlcke wrote:
> clang doesn't raise
> warnings about unused static inline functions in headers.
Is any "#include" file a "header" to clang or only "*.h" files?
For instance:
The kernel has ~500 .c files that other .c files #include.
Are unused inline functions in those .c files reported?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-25 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 21:01 [patch] compiler, clang: suppress warning for unused static inline functions 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
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 [this message]
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=1495730933.29207.6.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.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;
as well as URLs for NNTP newsgroup(s).