From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] ARM: ux500: select the DB8540 pin controller
Date: Mon, 28 Jan 2013 15:00:59 -0800 [thread overview]
Message-ID: <20130128230059.GE7789@quad.lixom.net> (raw)
In-Reply-To: <1359381151-28127-1-git-send-email-linus.walleij@stericsson.com>
On Mon, Jan 28, 2013 at 02:52:31PM +0100, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
>
> The pin controller is an inherent part of the SoC, without
> it the system will not boot, thus it needs to be selected
> from Kconfig.
>
> Cc: arm at kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Requesting ACK from ARM SoC on this patch.
Acked-by: Olof Johansson <olof@lixom.net>
... but I wonder if this is growing out of hand. Since they will always
be selected (and required) for UX500_SOC_DB8500, why not just make them
silent options that default to y with that as a depend?
-Olof
next prev parent reply other threads:[~2013-01-28 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 13:52 [PATCH 5/5] ARM: ux500: select the DB8540 pin controller Linus Walleij
2013-01-28 23:00 ` Olof Johansson [this message]
2013-01-29 18:16 ` Linus Walleij
2013-01-29 18:51 ` Olof Johansson
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=20130128230059.GE7789@quad.lixom.net \
--to=olof@lixom.net \
--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