mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@marvell.com>
To: <sebastian.hesselbarth@gmail.com>, <linus.walleij@linaro.org>,
	<antoine.tenart@free-electrons.com>, <catalin.marinas@arm.com>,
	<will.deacon@arm.com>, <mark.rutland@arm.com>,
	<robh+dt@kernel.org>, <pawel.moll@arm.com>,
	<ijc+devicetree@hellion.org.uk>, <galak@codeaurora.org>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Jisheng Zhang <jszhang@marvell.com>
Subject: [PATCH v6 2/7] pinctrl: berlin: Make berlin pinctrl driver visible if COMPILE_TEST=y
Date: Fri, 16 Oct 2015 15:37:07 +0800	[thread overview]
Message-ID: <1444981032-4401-3-git-send-email-jszhang@marvell.com> (raw)
In-Reply-To: <1444981032-4401-1-git-send-email-jszhang@marvell.com>

It is good to allow berlin pinctrl driver to build with COMPILE_TEST, so
make the it menu visible when compile-testing.

Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Acked-by: Antoine Tenart <antoine.tenart@free-electrons.com>
---
 drivers/pinctrl/berlin/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/pinctrl/berlin/Kconfig b/drivers/pinctrl/berlin/Kconfig
index b18322b..f7e45c8 100644
--- a/drivers/pinctrl/berlin/Kconfig
+++ b/drivers/pinctrl/berlin/Kconfig
@@ -1,4 +1,4 @@
-if ARCH_BERLIN
+if (ARCH_BERLIN || COMPILE_TEST)
 
 config PINCTRL_BERLIN
 	bool
-- 
2.6.1


  parent reply	other threads:[~2015-10-16  7:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  7:37 [PATCH v6 0/7] arm64: berlin: add pinctrl support Jisheng Zhang
2015-10-16  7:37 ` [PATCH v6 1/7] pinctrl: berlin: introduce berlin_pinctrl_probe_regmap() Jisheng Zhang
2015-10-16 14:11   ` Linus Walleij
2015-10-16  7:37 ` Jisheng Zhang [this message]
2015-10-16 14:12   ` [PATCH v6 2/7] pinctrl: berlin: Make berlin pinctrl driver visible if COMPILE_TEST=y Linus Walleij
2015-10-16  7:37 ` [PATCH v6 3/7] pinctrl: berlin: add the berlin4ct pinctrl driver Jisheng Zhang
2015-10-16 14:13   ` Linus Walleij
2015-10-16  7:37 ` [PATCH v6 4/7] arm64: berlin: add the pinctrl dependency for Marvell Berlin SoCs Jisheng Zhang
2015-10-16 14:15   ` Linus Walleij
2015-10-16 20:20     ` Sebastian Hesselbarth
2015-10-16  7:37 ` [PATCH v6 5/7] pinctrl: dt-binding: document berlin4ct SoC pinctrl Jisheng Zhang
2015-10-16 14:16   ` Linus Walleij
2015-10-16  7:37 ` [PATCH v6 6/7] arm64: dts: berlin4ct: add the pinctrl node Jisheng Zhang
2015-10-16 14:17   ` Linus Walleij
2015-10-16 20:10     ` Sebastian Hesselbarth
2015-10-16  7:37 ` [PATCH v6 7/7] arm64: dts: berlin4ct: add default pinmux for uart0 Jisheng Zhang
2015-10-16 14:18   ` Linus Walleij
2015-10-16 20:10     ` Sebastian Hesselbarth

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=1444981032-4401-3-git-send-email-jszhang@marvell.com \
    --to=jszhang@marvell.com \
    --cc=antoine.tenart@free-electrons.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=will.deacon@arm.com \
    /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

all inboxes | Powered by JetHome®