From: Frank Li <Frank.li@nxp.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Saravana Kannan" <saravanak@google.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Richard Zhu" <hongxing.zhu@nxp.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, "Conor Dooley" <conor.dooley@microchip.com>
Subject: Re: [PATCH v8 0/7] PCI: dwc: opitimaze RC Host/EP pci_fixup_addr()
Date: Thu, 19 Dec 2024 14:55:08 -0500 [thread overview]
Message-ID: <Z2R6HET6FZEO+uwi@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <Z1i9uEGvsVACsF2r@lizhi-Precision-Tower-5810>
On Tue, Dec 10, 2024 at 05:16:24PM -0500, Frank Li wrote:
> On Sun, Nov 24, 2024 at 08:08:39PM +0530, Manivannan Sadhasivam wrote:
> > On Tue, Nov 19, 2024 at 02:44:18PM -0500, Frank Li wrote:
[...]
> > > Previously, `cpu_addr_fixup()` was used to handle address conversion. Now,
> > > the device tree provides this information.
> > >
> > > The both pave the road to eliminate ugle cpu_fixup_addr() callback function.
> > >
> >
> > Series looks good to me. Thanks a lot for your persistence! But it missed 6.13
> > cycle. So let's get it merged early once 6.13-rc1 is out.
>
> Krzysztof Wilczyński:
>
> Could you please pick these? all reviewed by mani? It pave the
> road to clean up ugle cpu_fixup_addr().
Krzysztof Wilczyński and Bjorn Helgaas
Any update for this? All already reviewed by mani.
Frank
>
> Frank
>
> >
> > - Mani
> >
[...]
> >
> > --
> > மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-12-19 19:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 19:44 [PATCH v8 0/7] PCI: dwc: opitimaze RC Host/EP pci_fixup_addr() Frank Li
2024-11-19 19:44 ` [PATCH v8 1/7] of: address: Add parent_bus_addr to struct of_pci_range Frank Li
2024-11-19 19:44 ` [PATCH v8 2/7] PCI: dwc: Use devicetree 'ranges' property to get rid of cpu_addr_fixup() callback Frank Li
2024-11-24 14:33 ` Manivannan Sadhasivam
2025-01-16 1:47 ` Krzysztof Wilczyński
2025-01-16 1:56 ` Frank Li
2025-01-16 23:13 ` Bjorn Helgaas
2025-01-16 23:29 ` Bjorn Helgaas
2025-01-17 15:42 ` Frank Li
2025-01-23 15:21 ` Frank Li
2025-01-23 19:04 ` Bjorn Helgaas
2025-01-23 19:15 ` Frank Li
2025-01-27 15:24 ` Niklas Cassel
2025-01-23 19:09 ` Bjorn Helgaas
2025-01-17 15:50 ` Frank Li
2024-11-19 19:44 ` [PATCH v8 3/7] PCI: dwc: ep: Add bus_addr_base for outbound window Frank Li
2025-01-16 15:32 ` Bjorn Helgaas
2025-01-16 18:04 ` Frank Li
2025-01-16 19:45 ` Bjorn Helgaas
2025-01-16 20:02 ` Frank Li
2025-01-16 22:49 ` Bjorn Helgaas
2025-01-17 14:35 ` Manivannan Sadhasivam
2025-01-17 15:17 ` Frank Li
2024-11-19 19:44 ` [PATCH v8 4/7] PCI: imx6: Remove cpu_addr_fixup() Frank Li
2024-11-19 19:44 ` [PATCH v8 5/7] dt-bindings: PCI: fsl,imx6q-pcie-ep: Add compatible string fsl,imx8q-pcie-ep Frank Li
2024-11-19 19:44 ` [PATCH v8 6/7] PCI: imx6: Pass correct sub mode when calling phy_set_mode_ext() Frank Li
2024-11-19 19:44 ` [PATCH v8 7/7] PCI: imx6: Add i.MX8Q PCIe Endpoint (EP) support Frank Li
2024-11-24 14:38 ` [PATCH v8 0/7] PCI: dwc: opitimaze RC Host/EP pci_fixup_addr() Manivannan Sadhasivam
2024-12-10 22:16 ` Frank Li
2024-12-19 19:55 ` Frank Li [this message]
2025-01-06 17:14 ` Frank Li
2025-01-07 17:59 ` Frank Li
2025-01-16 1:56 ` Krzysztof Wilczyński
2025-01-15 11:42 ` Krzysztof Wilczyński
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=Z2R6HET6FZEO+uwi@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kw@linux.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawnguo@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