From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH] regulator: core: mark lock functions as __maybe_unused
Date: Wed, 7 Oct 2015 11:24:07 +0100 [thread overview]
Message-ID: <20151007102407.GF12635@sirena.org.uk> (raw)
In-Reply-To: <6130994.OMIWUN9F6x@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
On Wed, Oct 07, 2015 at 12:12:09PM +0200, Arnd Bergmann wrote:
> The best way to avoid these would be to add the code that will
> use these functions. If that still takes a while, this patch
> at least shuts up the compiler by marking the functions
> as __maybe_unused. The same could be achieved by marking them
> as static inline or non-static, or by hiding them from the
> compiler, but those seemed less appropriate.
That code is still in review, it's not looking too hard to get merged.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-07 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 10:12 Arnd Bergmann
2015-10-07 10:24 ` Mark Brown [this message]
2015-10-07 14:01 ` Sascha Hauer
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=20151007102407.GF12635@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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
Powered by JetHome