From: Mark Brown <broonie@opensource•wolfsonmicro.com>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Samuel Ortiz <sameo@linux•intel.com>,
Margarita Olaya <magi@slimlogic•co.uk>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH -next] mfd: tps65912 needs MFD_CORE
Date: Wed, 22 Jun 2011 19:29:15 +0100 [thread overview]
Message-ID: <20110622182915.GA13847@sirena.org.uk> (raw)
In-Reply-To: <20110622100615.c79765ff.randy.dunlap@oracle.com>
On Wed, Jun 22, 2011 at 10:06:15AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle•com>
>
> MFD_TPS65912 should select MFD_CORE so that mfd interfaces are
> available to it. This fixes a build error when MFD_CORE=m and
> MFD_TPS65912=y (and no other TPS65912 kconfig symbols are enabled,
> so no other select MFD_CORE was done).
I posted a better patch for this earlier today - the bigger problem here
is that as with other MFD cores MFD_TPS65912 shouldn't be directly
selectable at all as it can't do anything useful without a bus
interface.
next prev parent reply other threads:[~2011-06-22 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 6:36 linux-next: Tree for June 22 Stephen Rothwell
2011-06-22 17:06 ` [PATCH -next] mfd: tps65912 needs MFD_CORE Randy Dunlap
2011-06-22 18:29 ` Mark Brown [this message]
2011-06-22 18:46 ` Randy Dunlap
2011-06-22 17:08 ` [PATCH -next] bluetooth: uses crypto interfaces, select CRYPTO Randy Dunlap
[not found] ` <20110622100811.258091ff.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-06-27 18:03 ` Randy Dunlap
[not found] ` <20110627110308.dc64e3a7.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-06-27 18:13 ` Gustavo F. Padovan
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=20110622182915.GA13847@sirena.org.uk \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=magi@slimlogic$(echo .)co.uk \
--cc=randy.dunlap@oracle$(echo .)com \
--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