From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: solve some Kconfig mess
Date: Wed, 29 Feb 2012 20:13:26 +0000 [thread overview]
Message-ID: <201202292013.26661.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdaqdmB0_Z9FYC97FWZ2+RBSMfErUa62y0icqSOqAo8o1g@mail.gmail.com>
On Wednesday 29 February 2012, Linus Walleij wrote:
> On Wed, Feb 29, 2012 at 8:28 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>
> > Looks good to me. One thing I still wonder about is whether
> > we should leave the UX500_SOC_DB5500 and UX500_SOC_DB8500
> > options user-visible. It would probably be simpler to just
> > select these whenever a board using them is enabled.
>
> They are invisible to me atleast?
>
> config UX500_SOC_DB5500
> bool
> select MFD_DB5500_PRCMU
>
> config UX500_SOC_DB8500
> bool
> select MFD_DB8500_PRCMU
> select REGULATOR_DB8500_PRCMU
> select CPU_FREQ_TABLE if CPU_FREQ
>
Ah, I forgot that I had actually done that patch myself and
Mathieu sent it last week, so now it's in your tree but not mine.
Nevermind then.
Arnd
prev parent reply other threads:[~2012-02-29 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:28 [PATCH] ARM: ux500: solve some Kconfig mess Linus Walleij
2012-02-29 19:28 ` Arnd Bergmann
2012-02-29 19:43 ` Linus Walleij
2012-02-29 20:13 ` Arnd Bergmann [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=201202292013.26661.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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