From: "Måns Rullgård" <mans@mansr.com>
To: Behan Webster <behanw@converseincode.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
"Christopher Li" <sparse@chrisli.org>
Subject: Re: [PATCH] Mark inline functions as __maybe_unused
Date: Wed, 28 Jan 2015 10:04:34 +0000 [thread overview]
Message-ID: <yw1xtwzbb4r1.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <1422422779-3876-1-git-send-email-behanw@converseincode.com> (Behan Webster's message of "Tue, 27 Jan 2015 21:26:19 -0800")
Behan Webster <behanw@converseincode.com> writes:
> clang warns if inline functions aren't used. By making them __maybe_unused
> there is no warning for either gcc nor clang.
Are you sure about that? I've never seen such behaviour from clang (or
any other compiler), and it would truly be idiotic. If clang has taken
to warning about unused inline functions, that's a regression that needs
to be addressed in clang, not the kernel.
--
Måns Rullgård
mans@mansr.com
prev parent reply other threads:[~2015-01-28 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 5:26 Behan Webster
2015-01-28 10:04 ` Måns Rullgård [this message]
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=yw1xtwzbb4r1.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=arnd@arndb.de \
--cc=behanw@converseincode.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®