From: "Michael Büsch" <m@bues.ch>
To: Arnd Bergmann <arnd@arndb.de>
Cc: netdev@vger.kernel.org, Kalle Valo <kvalo@codeaurora.org>,
linux-kernel@vger.kernel.org, zajec5@gmail.com,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [PATCH] ssb: mark ssb_bus_register as __maybe_unused
Date: Tue, 3 Nov 2015 17:27:21 +0100 [thread overview]
Message-ID: <20151103172721.04533081@wiggum> (raw)
In-Reply-To: <5928552.0ccybX7Zly@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On Tue, 03 Nov 2015 16:05:51 +0100
Arnd Bergmann <arnd@arndb.de> wrote:
> The SoC variant of the ssb code is now optional like the other
> ones, which means we can build the framwork without any
> front-end, but that results in a warning:
>
> drivers/ssb/main.c:616:12: warning: 'ssb_bus_register' defined but not used [-Wunused-function]
>
> This annotates the ssb_bus_register function as __maybe_unused to
> shut up the warning. A configuration like this will not work on
> any hardware of course, but we still want this to silently build
> without warnings if the configuration is allowed in the first
> place.
Is there a simple way to disallow this configuration?
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-03 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 15:05 [PATCH] ssb: mark ssb_bus_register as __maybe_unused Arnd Bergmann
2015-11-03 15:59 ` [PATCH] ARM: at91/defconfig: remove CONFIG_SSB from Atmel defconfigs Nicolas Ferre
2015-11-03 15:59 ` Nicolas Ferre
2015-11-03 16:27 ` Michael Büsch [this message]
2015-11-03 16:42 ` [PATCH] ssb: mark ssb_bus_register as __maybe_unused Arnd Bergmann
2015-11-03 16:51 ` Michael Büsch
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=20151103172721.04533081@wiggum \
--to=m@bues.ch \
--cc=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.