From: Chen Wang <unicorn_wang@outlook.com>
To: "Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Bjorn Helgaas" <helgaas@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: sg2042: Fix a reference count issue in sg2042_pcie_remove()
Date: Sun, 19 Oct 2025 08:36:36 +0800 [thread overview]
Message-ID: <PN6PR01MB117174C06FE98FC0322A0B3F6FEF4A@PN6PR01MB11717.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <0e9b75d5-a1a6-4c5e-ad69-8e189af69bf3@outlook.com>
Hi,Bjorn,
I see you raise some fixes PRs for PCI for 6.18, can you please pick
this one also?
Thanks,
Chen
On 10/13/2025 10:31 AM, Chen Wang wrote:
> Hi,Manivannan,
>
> I see 6.18-rc1 is released. Could you please pick this fix for 6.18-rcX?
>
> Thanks,
>
> Chen
>
> On 9/30/2025 8:43 AM, Chen Wang wrote:
>>
>> On 9/30/2025 2:13 AM, Christophe JAILLET wrote:
>>> devm_pm_runtime_enable() is used in the probe, so pm_runtime_disable()
>>> should not be called explicitly in the remove function.
>>>
>>> Fixes: 1c72774df028 ("PCI: sg2042: Add Sophgo SG2042 PCIe driver")
>>> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>>
>> LGTM.
>>
>> Acked-by: Chen Wang <unicorn_wang@outlook.com>
>>
>> Tested-by: Chen Wang <unicorn_wang@outlook.com> # on Pioneerbox.
>>
>> Thanks,
>>
>> Chen
>>
>>> ---
>>> Compile tested only
>>> ---
>>> drivers/pci/controller/cadence/pcie-sg2042.c | 3 ---
>>> 1 file changed, 3 deletions(-)
>>>
>>> diff --git a/drivers/pci/controller/cadence/pcie-sg2042.c
>>> b/drivers/pci/controller/cadence/pcie-sg2042.c
>>> index a077b28d4894..0c50c74d03ee 100644
>>> --- a/drivers/pci/controller/cadence/pcie-sg2042.c
>>> +++ b/drivers/pci/controller/cadence/pcie-sg2042.c
>>> @@ -74,15 +74,12 @@ static int sg2042_pcie_probe(struct
>>> platform_device *pdev)
>>> static void sg2042_pcie_remove(struct platform_device *pdev)
>>> {
>>> struct cdns_pcie *pcie = platform_get_drvdata(pdev);
>>> - struct device *dev = &pdev->dev;
>>> struct cdns_pcie_rc *rc;
>>> rc = container_of(pcie, struct cdns_pcie_rc, pcie);
>>> cdns_pcie_host_disable(rc);
>>> cdns_pcie_disable_phy(pcie);
>>> -
>>> - pm_runtime_disable(dev);
>>> }
>>> static int sg2042_pcie_suspend_noirq(struct device *dev)
next prev parent reply other threads:[~2025-10-19 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 18:13 [PATCH] PCI: sg2042: Fix a reference count issue in sg2042_pcie_remove() Christophe JAILLET
2025-09-30 0:43 ` Chen Wang
[not found] ` <f1887014-17b5-405c-bba2-1a441d50e1f8@outlook.com>
2025-10-13 2:31 ` Chen Wang
2025-10-20 15:27 ` Bjorn Helgaas
2025-10-21 1:22 ` Manivannan Sadhasivam
[not found] ` <0e9b75d5-a1a6-4c5e-ad69-8e189af69bf3@outlook.com>
2025-10-19 0:36 ` Chen Wang [this message]
2025-10-20 5:18 ` Manivannan Sadhasivam
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=PN6PR01MB117174C06FE98FC0322A0B3F6FEF4A@PN6PR01MB11717.INDPRD01.PROD.OUTLOOK.COM \
--to=unicorn_wang@outlook.com \
--cc=bhelgaas@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=helgaas@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@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