From: James Liao <jamesjj.liao@mediatek.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Sascha Hauer <kernel@pengutronix.de>,
Kevin Hilman <khilman@kernel.org>,
Daniel Kurtz <djkurtz@chromium.org>,
srv_heupstream@mediatek.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/4] soc: mediatek: Separate scpsys driver common code
Date: Wed, 30 Dec 2015 18:08:42 +0800 [thread overview]
Message-ID: <1451470122.22426.1.camel@mtksdaap41> (raw)
In-Reply-To: <2524123.scG8tD5NSM@wuerfel>
Hi Arnd,
On Wed, 2015-12-30 at 09:52 +0100, Arnd Bergmann wrote:
> On Wednesday 30 December 2015 14:41:43 James Liao wrote:
> > diff --git a/drivers/soc/mediatek/Kconfig b/drivers/soc/mediatek/Kconfig
> > index 0a4ea80..eca6fb7 100644
> > --- a/drivers/soc/mediatek/Kconfig
> > +++ b/drivers/soc/mediatek/Kconfig
> > @@ -22,11 +22,20 @@ config MTK_PMIC_WRAP
> >
> > config MTK_SCPSYS
> > bool "MediaTek SCPSYS Support"
> > - depends on ARCH_MEDIATEK || COMPILE_TEST
> > - default ARM64 && ARCH_MEDIATEK
> > select REGMAP
> > select MTK_INFRACFG
> > select PM_GENERIC_DOMAINS if PM
> > help
> > Say yes here to add support for the MediaTek SCPSYS power domain
> > driver.
> > +
> > +config MTK_SCPSYS_MT8173
> > + bool "MediaTek MT8173 SCPSYS Support"
> > + depends on ARCH_MEDIATEK || COMPILE_TEST
> > + select MTK_SCPSYS
> > + default ARCH_MEDIATEK
> >
>
> Please don't "select" a user-visible Kconfig symbol. Either hide MTK_SCPSYS
> by removing the string behind 'bool', or make this "depends on MTK_SCPSYS".
It looks something wrong during cherry-pick. MTK_SCPSYS should be
invisible from user. I'll remove the string behind 'bool' in next patch.
Best regards,
James
next prev parent reply other threads:[~2015-12-30 10:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 6:41 [PATCH 0/4] Mediatek MT2701 SCPSYS power domain support James Liao
[not found] ` <1451457706-14798-1-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30 6:41 ` [PATCH 1/4] soc: mediatek: Separate scpsys driver common code James Liao
2015-12-30 8:52 ` Arnd Bergmann
2015-12-30 10:08 ` James Liao [this message]
2015-12-30 6:41 ` [PATCH 2/4] soc: mediatek: Init MT8173 scpsys driver earlier James Liao
[not found] ` <1451457706-14798-3-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30 8:52 ` Arnd Bergmann
2015-12-30 10:12 ` James Liao
2015-12-30 10:35 ` Arnd Bergmann
2015-12-31 5:59 ` James Liao
2015-12-31 9:16 ` James Liao
2015-12-31 14:45 ` Arnd Bergmann
2016-01-04 2:52 ` James Liao
2015-12-30 6:41 ` [PATCH 3/4] soc: mediatek: Add MT2701 power dt-bindings James Liao
2015-12-30 6:41 ` [PATCH 4/4] soc: mediatek: Add MT2701/MT7623 scpsys driver James Liao
[not found] ` <1451457706-14798-5-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30 9:01 ` Daniel Kurtz
2015-12-30 10:18 ` James Liao
2015-12-30 17:49 ` Matthias Brugger
2016-01-05 5:23 ` James Liao
2016-01-08 11:26 ` Matthias Brugger
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=1451470122.22426.1.camel@mtksdaap41 \
--to=jamesjj.liao@mediatek.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=kernel@pengutronix.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=srv_heupstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).