linux-kernel - Re: [PATCH v2 0/3] net: phy: switch to using fwnode_gpiod_get

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: <20191105.100423.1742603284030008698.davem@davemloft.net>
Date:   Tue, 05 Nov 2019 10:04:23 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     dmitry.torokhov@...il.com
Cc:     linux@...linux.org.uk, linus.walleij@...aro.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        andrew@...n.ch, f.fainelli@...il.com, hkallweit1@...il.com
Subject: Re: [PATCH v2 0/3] net: phy: switch to using fwnode_gpiod_get_index

From: Dmitry Torokhov <dmitry.torokhov@...il.com>
Date: Tue, 5 Nov 2019 09:27:51 -0800

> On Mon, Nov 4, 2019 at 4:55 PM Russell King - ARM Linux admin
> <linux@...linux.org.uk> wrote:
>>
>> On Mon, Nov 04, 2019 at 04:40:16PM -0800, Dmitry Torokhov wrote:
>> > Hi Linus,
>> >
>> > On Mon, Oct 14, 2019 at 10:40:19AM -0700, Dmitry Torokhov wrote:
>> > > This series switches phy drivers form using fwnode_get_named_gpiod() and
>> > > gpiod_get_from_of_node() that are scheduled to be removed in favor
>> > > of fwnode_gpiod_get_index() that behaves more like standard
>> > > gpiod_get_index() and will potentially handle secondary software
>> > > nodes in cases we need to augment platform firmware.
>> > >
>> > > Linus, as David would prefer not to pull in the immutable branch but
>> > > rather route the patches through the tree that has the new API, could
>> > > you please take them with his ACKs?
>> >
>> > Gentle ping on the series...
>>
>> Given that kbuild found a build issue with patch 1, aren't we waiting
>> for you to produce an updated patch 1?
> 
> No: kbuild is unable to parse instructions such as "please pull an
> immutable branch" before applying the series. Linus' tree already has
> needed changes.

This is targetting the networking tree so it doesn't matter what is in
Linus's tree, it has to build against MY tree and that's what Kbuild
tests against.

Resubmit if it builds against my tree, and no sooner.