All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Minghuan Lian <minghuan.Lian@nxp.com>,
	Mingkai Hu <mingkai.hu@nxp.com>, Roy Zang <roy.zang@nxp.com>,
	Rob Herring <robh@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Saravana Kannan <saravanak@google.com>
Subject: Re: [PATCH] PCI: dwc: layerscape: convert to builtin_platform_driver()
Date: Tue, 26 Jan 2021 11:39:54 +0100	[thread overview]
Message-ID: <1a36ef741c5ab2a6e90b38c58944aa25@walle.cc> (raw)
In-Reply-To: <20210126100256.GA20547@e121166-lin.cambridge.arm.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Michael Walle <michael@walle.cc>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Roy Zang <roy.zang@nxp.com>,
	Saravana Kannan <saravanak@google.com>,
	Rob Herring <robh@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Minghuan Lian <minghuan.Lian@nxp.com>,
	linux-arm-kernel@lists.infradead.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linuxppc-dev@lists.ozlabs.org, Mingkai Hu <mingkai.hu@nxp.com>
Subject: Re: [PATCH] PCI: dwc: layerscape: convert to builtin_platform_driver()
Date: Tue, 26 Jan 2021 11:39:54 +0100	[thread overview]
Message-ID: <1a36ef741c5ab2a6e90b38c58944aa25@walle.cc> (raw)
In-Reply-To: <20210126100256.GA20547@e121166-lin.cambridge.arm.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Michael Walle <michael@walle.cc>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Roy Zang <roy.zang@nxp.com>,
	Saravana Kannan <saravanak@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Minghuan Lian <minghuan.Lian@nxp.com>,
	linux-arm-kernel@lists.infradead.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linuxppc-dev@lists.ozlabs.org, Mingkai Hu <mingkai.hu@nxp.com>
Subject: Re: [PATCH] PCI: dwc: layerscape: convert to builtin_platform_driver()
Date: Tue, 26 Jan 2021 11:39:54 +0100	[thread overview]
Message-ID: <1a36ef741c5ab2a6e90b38c58944aa25@walle.cc> (raw)
In-Reply-To: <20210126100256.GA20547@e121166-lin.cambridge.arm.com>

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-01-26 11:39 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 10:52 [PATCH] PCI: dwc: layerscape: convert to builtin_platform_driver() Michael Walle
2021-01-20 10:52 ` Michael Walle
2021-01-20 10:52 ` Michael Walle
2021-01-20 14:23 ` Rob Herring
2021-01-20 14:23   ` Rob Herring
2021-01-20 14:23   ` Rob Herring
2021-01-20 14:34   ` Michael Walle
2021-01-20 14:34     ` Michael Walle
2021-01-20 14:34     ` Michael Walle
2021-01-20 15:50   ` Greg Kroah-Hartman
2021-01-20 15:50     ` Greg Kroah-Hartman
2021-01-20 15:50     ` Greg Kroah-Hartman
2021-01-20 19:02   ` Saravana Kannan
2021-01-20 19:02     ` Saravana Kannan
2021-01-20 19:02     ` Saravana Kannan
2021-01-20 19:25     ` Michael Walle
2021-01-20 19:28     ` Michael Walle
2021-01-20 19:28       ` Michael Walle
2021-01-20 19:28       ` Michael Walle
2021-01-20 19:47       ` Saravana Kannan
2021-01-20 19:47         ` Saravana Kannan
2021-01-20 19:47         ` Saravana Kannan
2021-01-20 19:47         ` Saravana Kannan
2021-01-20 19:47           ` Saravana Kannan
2021-01-20 19:47           ` Saravana Kannan
2021-01-20 23:53         ` Michael Walle
2021-01-20 23:53           ` Michael Walle
2021-01-20 23:53           ` Michael Walle
2021-01-20 23:58           ` Saravana Kannan
2021-01-20 23:58             ` Saravana Kannan
2021-01-20 23:58             ` Saravana Kannan
2021-01-21 11:01             ` Geert Uytterhoeven
2021-01-21 11:01               ` Geert Uytterhoeven
2021-01-21 11:01               ` Geert Uytterhoeven
2021-01-25 19:49               ` Michael Walle
2021-01-25 19:49                 ` Michael Walle
2021-01-25 19:49                 ` Michael Walle
2021-01-25 22:41                 ` Saravana Kannan
2021-01-25 22:41                   ` Saravana Kannan
2021-01-25 22:41                   ` Saravana Kannan
2021-01-26  8:50                   ` Geert Uytterhoeven
2021-01-26  8:50                     ` Geert Uytterhoeven
2021-01-26  8:50                     ` Geert Uytterhoeven
2021-01-27  0:44                     ` Saravana Kannan
2021-01-27  0:44                       ` Saravana Kannan
2021-01-27  0:44                       ` Saravana Kannan
2021-01-27  7:43                       ` Geert Uytterhoeven
2021-01-27  7:43                         ` Geert Uytterhoeven
2021-01-27  7:43                         ` Geert Uytterhoeven
2021-01-27 16:41                         ` Saravana Kannan
2021-01-27 16:41                           ` Saravana Kannan
2021-01-27 16:41                           ` Saravana Kannan
2021-01-27 16:56                           ` Geert Uytterhoeven
2021-01-27 16:56                             ` Geert Uytterhoeven
2021-01-27 16:56                             ` Geert Uytterhoeven
2021-01-27 17:10                             ` Saravana Kannan
2021-01-27 17:10                               ` Saravana Kannan
2021-01-27 17:10                               ` Saravana Kannan
2021-01-28  9:25                               ` Geert Uytterhoeven
2021-01-28  9:25                                 ` Geert Uytterhoeven
2021-01-28  9:25                                 ` Geert Uytterhoeven
2021-01-28 10:35                                 ` Tony Lindgren
2021-01-28 10:35                                   ` Tony Lindgren
2021-01-28 10:35                                   ` Tony Lindgren
2021-01-28 10:00                 ` Tony Lindgren
2021-01-28 10:00                   ` Tony Lindgren
2021-01-28 10:00                   ` Tony Lindgren
2021-01-25 16:50       ` Lorenzo Pieralisi
2021-01-25 16:50         ` Lorenzo Pieralisi
2021-01-25 16:50         ` Lorenzo Pieralisi
2021-01-25 18:58         ` Saravana Kannan
2021-01-25 18:58           ` Saravana Kannan
2021-01-25 18:58           ` Saravana Kannan
2021-01-25 19:44           ` Michael Walle
2021-01-25 19:44             ` Michael Walle
2021-01-25 19:44             ` Michael Walle
2021-01-26 10:02 ` Lorenzo Pieralisi
2021-01-26 10:02   ` Lorenzo Pieralisi
2021-01-26 10:02   ` Lorenzo Pieralisi
2021-01-26 10:39   ` Michael Walle [this message]
2021-01-26 10:39     ` Michael Walle
2021-01-26 10:39     ` Michael Walle
2021-01-26 10:56     ` Geert Uytterhoeven
2021-01-26 10:56       ` Geert Uytterhoeven
2021-01-26 10:56       ` Geert Uytterhoeven
2021-01-26 10:55 ` Lorenzo Pieralisi
2021-01-26 10:55   ` Lorenzo Pieralisi
2021-01-26 10:55   ` Lorenzo Pieralisi

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=1a36ef741c5ab2a6e90b38c58944aa25@walle.cc \
    --to=michael@walle.cc \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=minghuan.Lian@nxp.com \
    --cc=mingkai.hu@nxp.com \
    --cc=robh@kernel.org \
    --cc=roy.zang@nxp.com \
    --cc=saravanak@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.