linux-kernel - Re: [PATCH 2/2] mfd: remove use of gpiochip

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] [day] [month] [year] [list]

Message-ID: <20141007100228.GZ25331@lee--X1>
Date:	Tue, 7 Oct 2014 11:02:28 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Pramod Gurav <pramod.gurav@...rtplayin.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Alexandre Courbot <gnurou@...il.com>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 2/2] mfd: remove use of gpiochip_remove() retval

On Tue, 07 Oct 2014, Linus Walleij wrote:

> On Tue, Oct 7, 2014 at 11:14 AM, Lee Jones <lee.jones@...aro.org> wrote:
> > On Wed, 01 Oct 2014, Linus Walleij wrote:
> >
> >> On Tue, Sep 30, 2014 at 4:15 PM, Pramod Gurav
> >> <pramod.gurav@...rtplayin.com> wrote:
> >>
> >> > Get rid of using return value from gpiochip_remove() as it returns
> >> > void.
> >> >
> >> > Cc: Linus Walleij <linus.walleij@...aro.org>
> >> > Cc: Alexandre Courbot <gnurou@...il.com>
> >> > Cc: Samuel Ortiz <sameo@...ux.intel.com>
> >> > CC: Lee Jones <lee.jones@...aro.org>
> >> > Cc: linux-gpio@...r.kernel.org
> >> >
> >> > Signed-off-by: Pramod Gurav <pramod.gurav@...rtplayin.com>
> >>
> >> Already fixed in the GPIO tree.
> >
> > What does that mean?  That it doesn't need fixing here?
> 
> No. I think you already ACKed the patch fixing it in the GPIO
> tree...

No I don't need to apply the patch 'cos it's already fixed? Or, no
it's not already fixed and I need to apply the patch?

> There has been some misunderstanding and duplicate patches
> fixing already fixed problems are flying around.

I'm guessing from this commend that it _is_ already fixed and I _do
not_ need to apply this patch.

So for now I'm not applying this patch unless told otherwise.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/