linux-kernel - Re: [PATCH 18/19] ARM: SAMSUNG: Remove remaining legacy code

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1409825317.5546.94.camel@x220>
Date:	Thu, 04 Sep 2014 12:08:37 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Tomasz Figa <tomasz.figa@...il.com>
Cc:	linux-samsung-soc@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Kukjin Kim <kgene.kim@...sung.com>,
	Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Mark Brown <broonie@...nel.org>,
	Heiko Stübner <heiko@...ech.de>,
	Tomasz Figa <tomasz.figa@...il.com>
Subject: Re: [PATCH 18/19] ARM: SAMSUNG: Remove remaining legacy code

On Wed, 2014-07-16 at 15:00 +0200, Tomasz Figa wrote:
> On 16.07.2014 12:24, Paul Bolle wrote:
> > On Fri, 2014-07-04 at 19:48 +0200, Tomasz Figa wrote:
> >> -config S5P_GPIO_DRVSTR
> >> -	bool
> >> -	help
> >> -	  Internal configuration to get and set correct GPIO driver strength
> >> -	  helper
> >> -
> > 
> > This one is used (as a macro) in drivers/gpio/gpio-samsung.c. Is a patch
> > that touches that macro queued somewhere?
> 
> The code you mention should be removed as well as it's no longer needed.
> Will include in a follow-up series. Thanks for reporting this and
> remaining missed parts.

That check for CONFIG_S5P_GPIO_DRVSTR is still present in v3.17-rc3 and
next-20140903. Should I submit the trivial patch to remove it (and the
dead code it hides)?


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/