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: <CACRpkda21=_XZyDYYTAUB4PrKVGhNxz4X-Cubn_eSNn3GY9StQ@mail.gmail.com>
Date:	Sun, 13 Dec 2015 17:37:38 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
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 Wed, Dec 9, 2015 at 6:21 PM, Dmitry Torokhov
<dmitry.torokhov@...il.com> wrote:

>> > 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?
>>
>> I had to fuzz the patch so then you need to get the version I applied out
>> of my tree.
>>
>> But I'm not going to rebase the tree so you can pull commit
>> 9c3c9bc9cc980d8981f75109f3921576daf75723
>> from the GPIO tree if you like. Or I can make a tag there if
>> you prefer, just tell me.
>
> Both would mean I will end up with parts of your work-in-progress queue,
> which I would rather avoid. If you create a branch (lets call it A) off
> v4.3 and apply that one patch there and merge branch A it into your main
> branch (even though you already have a version of the same patch in your
> main branch) and I will merge that branch A into my tree then we are
> guaranteed not to have conflicts as git will resolve everything nicely.

I can't do that, as this patch is not applying cleanly on v4.3.

It applies cleanly to v4.4-rc1 though, would you like an immutable
branch like such based on v4.4-rc1 instead?

Linus Walleij
--
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/