On Thu, Sep 18, 2014 at 10:57 AM, Paul Bolle wrote:
> From: Paul Bolle
>
> Commit d78c16ccde96 ("ARM: SAMSUNG: Remove remaining legacy code")
> removed the Kconfig symbol S5P_GPIO_DRVSTR. It didn't remove one check
> for the related macro. Remove that check and the dead code it hides.
>
>
On Thu, Sep 18, 2014 at 10:57 AM, Paul Bolle pebo...@tiscali.nl wrote:
From: Paul Bolle pebo...@tiscali.nl
Commit d78c16ccde96 (ARM: SAMSUNG: Remove remaining legacy code)
removed the Kconfig symbol S5P_GPIO_DRVSTR. It didn't remove one check
for the related macro. Remove that check and the
Paul,
On 18.09.2014 10:57, Paul Bolle wrote:
> On Thu, 2014-09-04 at 18:03 +0200, Arnd Bergmann wrote:
>> On Thursday 04 September 2014, Paul Bolle wrote:
>>> 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
On Thu, 2014-09-04 at 18:03 +0200, Arnd Bergmann wrote:
> On Thursday 04 September 2014, Paul Bolle wrote:
> > 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)?
>
> Yes, I
On Thu, 2014-09-04 at 18:03 +0200, Arnd Bergmann wrote:
On Thursday 04 September 2014, Paul Bolle wrote:
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)?
Yes, I think this
Paul,
On 18.09.2014 10:57, Paul Bolle wrote:
On Thu, 2014-09-04 at 18:03 +0200, Arnd Bergmann wrote:
On Thursday 04 September 2014, Paul Bolle wrote:
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
6 matches
Mail list logo
