From: Mark Brown <broonie@kernel.org>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
Support Opensource <support.opensource@diasemi.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Fabrice Gasnier <fabrice.gasnier@st.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
Icenowy Zheng <icenowy@aosc.io>
Subject: Re: [PATCH 11/12] regulator: stm32-vrefbuf: Fix W=1 build warning when CONFIG_OF=n
Date: Thu, 20 Aug 2020 11:51:48 +0100 [thread overview]
Message-ID: <20200820105148.GA5854@sirena.org.uk> (raw)
In-Reply-To: <20200820163232.54b59e1d@xhacker.debian>
[-- Attachment #1.1: Type: text/plain, Size: 337 bytes --]
On Thu, Aug 20, 2020 at 04:32:32PM +0800, Jisheng Zhang wrote:
> On Thu, 20 Aug 2020 10:13:12 +0200 Fabrice Gasnier wrote:
> > You could probably adopt "__maybe_unused" here ? E.g. like:
> __maybe_unused also fixes the warning. I'm not sure the maintainers' preference.
> which solution do you prefer?
__maybe_unused is a bit nicer.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-20 10:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200820152926.42c48840@xhacker.debian>
2020-08-20 7:32 ` [PATCH 01/12] regulator: 88pg86x: Fix W=1 build warning when CONFIG_OF=n Jisheng Zhang
2020-08-20 7:33 ` [PATCH 02/12] regulator: da9210: " Jisheng Zhang
2020-08-20 7:34 ` [PATCH 03/12] regulator: fan53555: " Jisheng Zhang
2020-08-20 7:34 ` [PATCH 04/12] regulator: fixed: Fix W=1 build warnings " Jisheng Zhang
2020-08-20 7:35 ` [PATCH 05/12] regulator: ltc3589: Fix W=1 build warning " Jisheng Zhang
2020-08-20 7:36 ` [PATCH 06/12] regulator: ltc3676: " Jisheng Zhang
2020-08-20 7:37 ` [PATCH 07/12] regulator: max1586: " Jisheng Zhang
2020-08-20 7:37 ` [PATCH 08/12] regulator: max77826: " Jisheng Zhang
2020-08-20 7:38 ` [PATCH 09/12] regulator: pwm: " Jisheng Zhang
2020-08-20 7:46 ` [PATCH 11/12] regulator: stm32-vrefbuf: " Jisheng Zhang
2020-08-20 8:13 ` Fabrice Gasnier
2020-08-20 8:32 ` Jisheng Zhang
2020-08-20 10:51 ` Mark Brown [this message]
2020-08-20 7:47 ` [PATCH 12/12] regulator: sy8106a: " Jisheng Zhang
2020-08-20 8:00 ` [PATCH 10/12] regulator: stm32-pwr: " Jisheng Zhang
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=20200820105148.GA5854@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=alexandre.torgue@st.com \
--cc=fabrice.gasnier@st.com \
--cc=icenowy@aosc.io \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=support.opensource@diasemi.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).