From: Shawn Guo <shawnguo2@yeah.net>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, l.stach@pengutronix.de,
lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, bhelgaas@google.com,
s.hauer@pengutronix.de, festevam@gmail.com,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
imx@lists.linux.dev, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] arm64: dts: imx8mq: Add linux,pci-domain into pcie-ep node
Date: Tue, 22 Apr 2025 09:47:54 +0800 [thread overview]
Message-ID: <aAb1SlxBsADlglrh@dragon> (raw)
In-Reply-To: <20250226024256.1678103-2-hongxing.zhu@nxp.com>
On Wed, Feb 26, 2025 at 10:42:55AM +0800, Richard Zhu wrote:
> Add linux,pci-domain into pcie-ep node of i.MX8MQ.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
Applied, thanks!
next prev parent reply other threads:[~2025-04-22 2:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 2:42 [PATCH v1 0/2] Use domain number replace the hardcodes Richard Zhu
2025-02-26 2:42 ` [PATCH v1 1/2] arm64: dts: imx8mq: Add linux,pci-domain into pcie-ep node Richard Zhu
2025-02-28 23:05 ` Frank Li
2025-03-12 4:09 ` Hongxing Zhu
2025-04-22 1:47 ` Shawn Guo [this message]
2025-02-26 2:42 ` [PATCH v1 2/2] PCI: imx6: Use domain number replace the hardcodes Richard Zhu
2025-02-26 22:08 ` Bjorn Helgaas
2025-02-28 23:04 ` Frank Li
2025-03-09 20:36 ` Krzysztof Wilczyński
2025-03-10 15:11 ` Bjorn Helgaas
2025-03-11 1:11 ` Hongxing Zhu
2025-03-11 15:54 ` Bjorn Helgaas
2025-03-12 4:05 ` Hongxing Zhu
2025-03-12 8:28 ` Lucas Stach
2025-03-12 14:22 ` Frank Li
2025-03-13 8:54 ` Lucas Stach
2025-03-13 16:06 ` Bjorn Helgaas
2025-03-13 16:26 ` Frank Li
2025-03-18 7:46 ` manivannan.sadhasivam
2025-03-12 15:04 ` Bjorn Helgaas
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=aAb1SlxBsADlglrh@dragon \
--to=shawnguo2@yeah.net \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--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=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;
as well as URLs for NNTP newsgroup(s).