From: Scott Branden <scott.branden@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-kernel@vger.kernel.org
Cc: bcm-kernel-feedback-list@broadcom.com, kraxel@redhat.com,
eric@anholt.net, Linus Walleij <linus.walleij@linaro.org>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: Always recurse into bcm folder
Date: Wed, 8 Jun 2016 15:56:46 -0700 [thread overview]
Message-ID: <5758A2AE.6030304@broadcom.com> (raw)
In-Reply-To: <1465422255-20716-1-git-send-email-f.fainelli@gmail.com>
Looks good.
On 16-06-08 02:44 PM, Florian Fainelli wrote:
> drivers/pinctrl/bcm/Makefile properly builds individual drivers based on
> their respective Kconfig symbols. ARCH_BCM is currently a menuconfig
> option from arch/arm/mach-bcm/Kconfig, which is fine, but prevents ARM64
> platforms which do not have such menuconfig option from building their
> pinctrl drivers, so let's get rid of that dependency.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Acked-by: Scott Branden <scott.branden@broadcom.com>
> ---
> drivers/pinctrl/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/Makefile b/drivers/pinctrl/Makefile
> index 25ec45090620..8ebd7b8e1621 100644
> --- a/drivers/pinctrl/Makefile
> +++ b/drivers/pinctrl/Makefile
> @@ -37,7 +37,7 @@ obj-$(CONFIG_PINCTRL_TB10X) += pinctrl-tb10x.o
> obj-$(CONFIG_PINCTRL_ST) += pinctrl-st.o
> obj-$(CONFIG_PINCTRL_ZYNQ) += pinctrl-zynq.o
>
> -obj-$(CONFIG_ARCH_BCM) += bcm/
> +obj-y += bcm/
> obj-$(CONFIG_PINCTRL_BERLIN) += berlin/
> obj-y += freescale/
> obj-$(CONFIG_X86) += intel/
>
Regards,
Scott
next prev parent reply other threads:[~2016-06-08 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 21:44 [PATCH] pinctrl: Always recurse into bcm folder Florian Fainelli
2016-06-08 22:56 ` Scott Branden [this message]
2016-06-13 6:52 ` Linus Walleij
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=5758A2AE.6030304@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=kraxel@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).