linux-kernel - Re: [PATCH v5 1/5] ARM: mediatek: Add config options for mediatek SoCs.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Jan 2015 11:16:40 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	"Joe. C" <yingjoe.chen@...iatek.com>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	Matthias Brugger <matthias.bgg@...il.com>,
	Hongzhou Yang <hongzhou.yang@...iatek.com>,
	Rob Herring <robh+dt@...nel.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Sascha Hauer <kernel@...gutronix.de>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Russell King <linux@....linux.org.uk>,
	Grant Likely <grant.likely@...aro.org>,
	Catalin Marinas <catalin.marinas@....com>,
	Vladimir Murzin <vladimir.murzin@....com>,
	Ashwin Chaugule <ashwin.chaugule@...aro.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>, dandan.he@...iatek.com,
	alan.cheng@...iatek.com, toby.liu@...iatek.com,
	maoguang.meng@...iatek.com, huang eddie <eddie.huang@...iatek.com>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...soft.com>
Subject: Re: [PATCH v5 1/5] ARM: mediatek: Add config options for mediatek
 SoCs.

Joe,

On Thu, 2015-01-22 at 13:54 +0100, Matthias Brugger wrote:
> 2015-01-21 6:28 GMT+01:00 Hongzhou Yang <hongzhou.yang@...iatek.com>:
> > From: Yingjoe Chen <yingjoe.chen@...iatek.com>
> >
> > The upcoming MTK pinctrl driver have a big pin table for each SoC
> > and we don't want to bloat the kernel binary if we don't need it.
> > Add config options so we can build for one SoC only.
> >
> > Acked-by: Linus Walleij <linus.walleij@...aro.org>
> > Signed-off-by: Yingjoe Chen <yingjoe.chen@...iatek.com>
> > Signed-off-by: Hongzhou Yang <hongzhou.yang@...iatek.com>
> 
> Applied to v3.20-next/soc

This became commit ad8a221e1f49 ("ARM: mediatek: Add config options for
mediatek SoCs.") in today's linux-next (ie, next-20150127). I noticed
because a script I use to check linux-next spotted a problem with it.

> > ---
> >  arch/arm/mach-mediatek/Kconfig | 22 +++++++++++++++++++++-
> >  1 file changed, 21 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/mach-mediatek/Kconfig b/arch/arm/mach-mediatek/Kconfig
> > index f73f588..f7e463c 100644
> > --- a/arch/arm/mach-mediatek/Kconfig
> > +++ b/arch/arm/mach-mediatek/Kconfig
> > @@ -1,6 +1,26 @@
> > -config ARCH_MEDIATEK
> > +menuconfig ARCH_MEDIATEK
> >         bool "Mediatek MT65xx & MT81xx SoC" if ARCH_MULTI_V7
> >         select ARM_GIC
> >         select MTK_TIMER
> >         help
> >           Support for Mediatek MT65xx & MT81xx SoCs
> > +
> > +if ARCH_MEDIATEK
> > +
> > +config MACH_MT6589
> > +       bool "MediaTek MT6589 SoCs support"
> > +       default ARCH_MEDIATEK
> > +
> > +config MACH_MT6592
> > +       bool "MediaTek MT6592 SoCs support"
> > +       default ARCH_MEDIATEK
> > +
> > +config MACH_MT8127
> > +       bool "MediaTek MT8127 SoCs support"
> > +       default ARCH_MEDIATEK
> > +
> > +config MACH_MT8135
> > +       bool "MediaTek MT8135 SoCs support"
> > +       default ARCH_MEDIATEK
> > +
> > +endif

None of these four new MACH_MT* Kconfig symbols are currently used in
linux-next. I assume that patches that actually use them (either as a
Kconfig symbol or as a CONFIG_* macro) are still pending. Is that
correct?

Thanks,


Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/