From: Mark Brown <broonie@opensource•wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Samuel Ortiz <sameo@linux•intel.com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: mfd tree build warning
Date: Tue, 24 Nov 2009 11:06:01 +0000 [thread overview]
Message-ID: <20091124110601.GA26097@sirena.org.uk> (raw)
In-Reply-To: <20091124164219.c5d54461.sfr@canb.auug.org.au>
On Tue, Nov 24, 2009 at 04:42:19PM +1100, Stephen Rothwell wrote:
> I have been getting these warnings from the x86_64 allmodconfig build for
> a long time:
> drivers/mfd/wm8350-regmap.c:3177:2: warning: #warning No WM8350 config modes supported - select at least one of the
> drivers/mfd/wm8350-regmap.c:3178:2: warning: #warning MFD_WM8350_CONFIG_MODE_n options from the board driver.
> This may not be a problem, I just thought I should let you know.
It's not a real problem. Any actual system using the driver will need
to have explicit code which registers the I2C device for the WM8350,
that code will need to set up the particular build for the board. The
build time warning is there to try to make it a bit more obvious what's
needed.
Allowing the driver to be built without one of these defined provides
build coverage which is helpful for subsystem maintainers.
I might send a patch taking away the compile time warning, I'm not sure
how likely it is that people will notice it.
prev parent reply other threads:[~2009-11-24 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 5:42 linux-next: mfd tree build warning Stephen Rothwell
2009-11-24 11:06 ` Mark Brown [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=20091124110601.GA26097@sirena.org.uk \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sameo@linux$(echo .)intel.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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