From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: mark cpus_have_hwcap as __maybe_unused
Date: Thu, 12 Nov 2015 14:57:59 +0000 [thread overview]
Message-ID: <20151112145759.GH5627@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <5369626.MJXv4CTaxt@wuerfel>
On Thu, Nov 12, 2015 at 03:20:16PM +0100, Arnd Bergmann wrote:
> cpus_have_hwcap() is defined as a 'static' function an only used in
> one place that is inside of an #ifdef, so we get a warning when
> the only user is disabled:
>
> arch/arm64/kernel/cpufeature.c:699:13: warning: 'cpus_have_hwcap' defined but not used [-Wunused-function]
>
> This marks the function as __maybe_unused, so the compiler knows that
> it can drop the function definition without warning about it.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: 37b01d53ceef ("arm64/HWCAP: Use system wide safe values")
> ---
> Found on arm64 allnoconfig
I applied this patch and the other two you just posted. Thanks.
--
Catalin
prev parent reply other threads:[~2015-11-12 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 14:20 [PATCH] ARM64: mark cpus_have_hwcap as __maybe_unused Arnd Bergmann
2015-11-12 14:57 ` Catalin Marinas [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=20151112145759.GH5627@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).