public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: qcom: enable GPIOLIB in Kconfig
Date: Sun, 30 Oct 2016 12:50:38 +0000	[thread overview]
Message-ID: <20161030125038.qp55gvscygvdiiym@localhost> (raw)
In-Reply-To: <20161021175608.19073-1-michael.scott@linaro.org>

On Fri, Oct 21, 2016 at 10:56:08AM -0700, Michael Scott wrote:
> While debugging a kernel image size issue, I discovered that if all
> non ARCH_QCOM configs in the ARM64 defconfig are disabled, the QCOM
> pinctrl drivers will not be built.
> 
> The QCOM pinctrl drivers have a dependency on GPIOLIB which was being
> selected when other ARCH configs were enabled, but ARCH_QCOM doesn't
> select GPIOLIB directly.  Let's select GPIOLIB here to ensure the pinctrl
> drivers are built for QCOM platforms.
> 
> Signed-off-by: Michael Scott <michael.scott@linaro.org>
> ---
>  arch/arm64/Kconfig.platforms | 1 +

Such patches are normally handled by arm-soc (cc'ed).

-- 
Catalin

      reply	other threads:[~2016-10-30 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 17:56 [PATCH] arm64: qcom: enable GPIOLIB in Kconfig Michael Scott
2016-10-30 12:50 ` Catalin Marinas [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=20161030125038.qp55gvscygvdiiym@localhost \
    --to=catalin.marinas@arm.com \
    --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