linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dmitry.torokhov@gmail.com
Cc: linux@armlinux.org.uk, linus.walleij@linaro.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com
Subject: Re: [PATCH v2 0/3] net: phy: switch to using fwnode_gpiod_get_index
Date: Tue, 05 Nov 2019 10:04:23 -0800 (PST)	[thread overview]
Message-ID: <20191105.100423.1742603284030008698.davem@davemloft.net> (raw)
In-Reply-To: <CAKdAkRQNWXjMdJ9F1Lu=8+rHWFJwoyWu6Lcc+LFesaSTz3wspg@mail.gmail.com>

From: Dmitry Torokhov <dmitry.torokhov@gmail.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@armlinux.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.

  reply	other threads:[~2019-11-05 18:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 17:40 [PATCH v2 0/3] net: phy: switch to using fwnode_gpiod_get_index Dmitry Torokhov
2019-10-14 17:40 ` [PATCH v2 1/3] net: phylink: switch to using fwnode_gpiod_get_index() Dmitry Torokhov
2019-10-14 17:55   ` Russell King - ARM Linux admin
2019-10-14 20:30   ` kbuild test robot
2019-10-15 13:02   ` kbuild test robot
2019-10-14 17:40 ` [PATCH v2 2/3] net: phy: fixed_phy: fix use-after-free when checking link GPIO Dmitry Torokhov
2019-10-15 12:54   ` Andrew Lunn
2019-10-14 17:40 ` [PATCH v2 3/3] net: phy: fixed_phy: switch to using fwnode_gpiod_get_index Dmitry Torokhov
2019-10-14 22:37   ` kbuild test robot
2019-10-16  3:18 ` [PATCH v2 0/3] net: phy: " David Miller
2019-11-05  0:40 ` Dmitry Torokhov
2019-11-05  0:55   ` Russell King - ARM Linux admin
2019-11-05 17:27     ` Dmitry Torokhov
2019-11-05 18:04       ` David Miller [this message]
2019-11-05 18:20         ` Dmitry Torokhov
2019-11-13 21:26           ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191105.100423.1742603284030008698.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=dmitry.torokhov@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).