[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1a36ef741c5ab2a6e90b38c58944aa25@walle.cc>
Date: Tue, 26 Jan 2021 11:39:54 +0100
From: Michael Walle <michael@...le.cc>
To: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Cc: linuxppc-dev@...ts.ozlabs.org, linux-pci@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Minghuan Lian <minghuan.Lian@....com>,
Mingkai Hu <mingkai.hu@....com>, Roy Zang <roy.zang@....com>,
Rob Herring <robh@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Saravana Kannan <saravanak@...gle.com>
Subject: Re: [PATCH] PCI: dwc: layerscape: convert to
builtin_platform_driver()
Am 2021-01-26 11:02, schrieb Lorenzo Pieralisi:
> On Wed, Jan 20, 2021 at 11:52:46AM +0100, Michael Walle wrote:
>> fw_devlink will defer the probe until all suppliers are ready. We
>> can't
>> use builtin_platform_driver_probe() because it doesn't retry after
>> probe
>> deferral. Convert it to builtin_platform_driver().
>>
>> Fixes: e590474768f1 ("driver core: Set fw_devlink=on by default")
>
> I will have to drop this Fixes: tag if you don't mind, it is not
> in the mainline.
That commit is in Greg's for-next tree:
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/commit/?h=driver-core-next&id=e590474768f1cc04852190b61dec692411b22e2a
I was under the impression there are other commits with this
particular fixes tag, too. Either it was removed from
for-next queues or I was confused.
But I'm fine with removing the tag, assuming this will end
up together with the "driver core: Set fw_devlink=on by default"
commit in 5.11.
-michael
Powered by blists - more mailing lists