From: Niklas Cassel <cassel@kernel.org>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>,
Manivannan Sadhasivam <mani@kernel.org>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Heiko Stuebner" <heiko@sntech.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] PCI: dwc: Remove duplicate dw_pcie_ep_hide_ext_capability() function
Date: Wed, 21 Jan 2026 11:13:12 +0100 [thread overview]
Message-ID: <aXCmuFA8JwmRofis@ryzen> (raw)
In-Reply-To: <aVPgL2AuAMpx76pI@ryzen>
On Tue, Dec 30, 2025 at 03:22:39PM +0100, Niklas Cassel wrote:
> Hello Qiang Yu,
>
> On Wed, Dec 24, 2025 at 02:10:46AM -0800, Qiang Yu wrote:
> > Remove dw_pcie_ep_hide_ext_capability() and replace its usage with
> > dw_pcie_remove_ext_capability(). Both functions serve the same purpose
> > of hiding PCIe extended capabilities, but dw_pcie_remove_ext_capability()
> > provides a cleaner API that doesn't require the caller to specify the
> > previous capability ID.
> >
> > Compile-tested only. Runtime testing on RK3588 hardware would be
> > appreciated.
>
> This patch does not appy on top of pci/controller/dwc
>
> Anyway, I applied it manually, and tested, thus:
> Tested-by: Niklas Cassel <cassel@kernel.org>
I just tried to apply this patch for pci/controller/dwc and right now,
this patch does apply.
Mani, any chance to get this picked up?
Kind regards,
Niklas
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-01-21 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 10:10 [PATCH] PCI: dwc: Remove duplicate dw_pcie_ep_hide_ext_capability() function Qiang Yu
2025-12-30 14:22 ` Niklas Cassel
2026-01-21 10:13 ` Niklas Cassel [this message]
2026-01-21 14:12 ` Manivannan Sadhasivam
2026-01-21 14:12 ` 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=aXCmuFA8JwmRofis@ryzen \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=heiko@sntech.de \
--cc=jingoohan1@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=qiang.yu@oss.qualcomm.com \
--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