From: Bjorn Helgaas <helgaas@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Krishna chaitanya chundru <quic_krichai@quicinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v3 0/2] PCI/pwrctl: fixes for v6.11
Date: Tue, 3 Sep 2024 17:13:11 -0500 [thread overview]
Message-ID: <20240903221311.GA306706@bhelgaas> (raw)
In-Reply-To: <20240823093323.33450-1-brgl@bgdev.pl>
On Fri, Aug 23, 2024 at 11:33:21AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Bjorn,
>
> Here's a respin of the PCI/pwrctl fixes that should go into v6.11. I
> eventually found a solution that doesn't require Krishna's topology
> change but Krishna: please make sure to update the code in
> drivers/pci/remove.c as well when rebasing your work once this gets
> upstream.
>
> v2 -> v3:
> - use the correct device for unregistering the platform pwrctl device in
> patch 1/2
> - make patch 1/2 easier to read by using device_for_each_child()
>
> v1 -> v2:
> - use the scoped variant of for_each_child_of_node() to fix a memory
> leak in patch 1/2
>
> Bartosz Golaszewski (2):
> PCI: don't rely on of_platform_depopulate() for reused OF-nodes
> PCI/pwrctl: put the bus rescan on a different thread
>
> drivers/pci/pwrctl/core.c | 26 +++++++++++++++++++++++---
> drivers/pci/pwrctl/pci-pwrctl-pwrseq.c | 2 +-
> drivers/pci/remove.c | 18 +++++++++++++++++-
> include/linux/pci-pwrctl.h | 3 +++
> 4 files changed, 44 insertions(+), 5 deletions(-)
Applied to pci/for-linus for v6.11, thanks.
prev parent reply other threads:[~2024-09-03 22:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 9:33 [PATCH v3 0/2] PCI/pwrctl: fixes for v6.11 Bartosz Golaszewski
2024-08-23 9:33 ` [PATCH v3 1/2] PCI: don't rely on of_platform_depopulate() for reused OF-nodes Bartosz Golaszewski
2024-08-23 22:10 ` Bjorn Helgaas
2024-08-24 7:49 ` Bartosz Golaszewski
2024-08-27 12:55 ` Rob Herring
2024-08-27 8:40 ` Manivannan Sadhasivam
2024-08-27 12:25 ` Bartosz Golaszewski
2024-08-27 14:09 ` Manivannan Sadhasivam
2024-08-23 9:33 ` [PATCH v3 2/2] PCI/pwrctl: put the bus rescan on a different thread Bartosz Golaszewski
2024-08-27 8:56 ` Manivannan Sadhasivam
2024-09-02 7:38 ` Bartosz Golaszewski
2024-09-02 7:42 ` [PATCH v3 0/2] PCI/pwrctl: fixes for v6.11 Bartosz Golaszewski
2024-09-03 22:13 ` Bjorn Helgaas [this message]
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=20240903221311.GA306706@bhelgaas \
--to=helgaas@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_krichai@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox