linux-kernel - Re: [PATCH v2] gpiolib: tighten up ACPI legacy gpio lookups

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: <20151127173721.GC27040@dtor-ws>
Date:	Fri, 27 Nov 2015 09:37:21 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Alexandre Courbot <gnurou@...il.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Johan Hovold <johan@...nel.org>,
	"Tirdea, Irina" <irina.tirdea@...el.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] gpiolib: tighten up ACPI legacy gpio lookups

On Tue, Nov 17, 2015 at 02:43:14PM +0100, Linus Walleij wrote:
> On Wed, Nov 11, 2015 at 8:45 PM, Dmitry Torokhov
> <dmitry.torokhov@...il.com> wrote:
> 
> > We should not fall back to the legacy unnamed gpio lookup style if the
> > driver requests gpios with different names, because we'll give out the same
> > gpio twice. Let's keep track of the names that were used for the device and
> > only do the fallback for the first name used.
> >
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@...il.com>
> > ---
> >
> > v1: incorporated changes suggested by Mika Westerberg in response to the
> > draft patch I posted in Goodix thread.
> >
> > v2: moved acpi_can_fallback_to_crs body to drivers/gpio/gpiolib-acpi.c
> > and provided stub for !CONFIG_ACPI case to fix build error if ACPI is
> > disabled.
> 
> Patch applied with Mika's ACK.
> 
> Had to fuzz a bit to make it apply, hope nothing breaks.

Hmm, I'd like to get this patch into my tree as well to apply Irina's
goodix pieces on top to make sure they do not break. Would it be OK for
me to just apply the patch and hope git will sort it out when we merge
into next/mainline, you maybe you could prepare a 4.3-based branch with
the patch for me to pull?

Thanks!

-- 
Dmitry
--
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/