From: Randy Dunlap <rdunlap@xenotime.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.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 11:46:47 -0700 [thread overview]
Message-ID: <20110622114647.0e8c1ec7.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110622182915.GA13847@sirena.org.uk>
On Wed, 22 Jun 2011 19:29:15 +0100 Mark Brown wrote:
> 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.
Good. Hopefully such a kconfig won't be possible in the
future then.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-06-22 18:47 UTC|newest]
Thread overview: 9+ 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
2011-06-22 18:46 ` Randy Dunlap [this message]
2011-06-22 17:08 ` [PATCH -next] bluetooth: uses crypto interfaces, select CRYPTO Randy Dunlap
2011-06-27 18:03 ` Randy Dunlap
2011-06-27 18:03 ` Randy Dunlap
2011-06-27 18:13 ` Gustavo F. Padovan
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=20110622114647.0e8c1ec7.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=magi@slimlogic.co.uk \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
/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.