From: Shawn Guo <shawnguo2@yeah.net>
To: Hongxing Zhu <hongxing.zhu@nxp.com>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>
Subject: Re: [PATCH v5 1/4] dt-bindings: imx6q-pcie: Add reg-name "dbi2" and "atu" for i.MX8M PCIe Endpoint
Date: Sat, 31 Aug 2024 20:59:53 +0800 [thread overview]
Message-ID: <ZtMTybL79ui5ocPM@dragon> (raw)
In-Reply-To: <AS8PR04MB86767916B0539B339120C2218C872@AS8PR04MB8676.eurprd04.prod.outlook.com>
On Wed, Aug 14, 2024 at 01:49:30AM +0000, Hongxing Zhu wrote:
> > Please add Acked-by/Reviewed-by tags when posting new versions. However,
> > there's no need to repost patches *only* to add the tags. The upstream
> > maintainer will do that for acks received on the version they apply.
> >
> > If a tag was not added on purpose, please state why and what changed.
> >
> > Missing tags:
> >
> > Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Hi Rob:
> Oops, I'm really sorry about that I missing this reviewed-by tag in v5 by
> my mistake.
> Thank you very much for your notice and kindly help.
>
> Hi Shawn:
> Can you help to pick-up Rob's reviewed-by tag?
> Thanks in advanced.
Hmm, this one should go via PCI tree.
Shawn
next prev parent reply other threads:[~2024-08-31 13:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 7:42 [PATCH v5 0/4] Add dbi2 and atu for i.MX8M PCIe EP Richard Zhu
2024-08-13 7:42 ` [PATCH v5 1/4] dt-bindings: imx6q-pcie: Add reg-name "dbi2" and "atu" for i.MX8M PCIe Endpoint Richard Zhu
2024-08-13 8:52 ` Krzysztof Kozlowski
2024-08-13 16:32 ` Rob Herring (Arm)
2024-08-14 1:49 ` Hongxing Zhu
2024-08-31 12:59 ` Shawn Guo [this message]
2024-09-02 2:08 ` Hongxing Zhu
2024-09-04 13:38 ` Frank Li
2024-09-06 6:31 ` Krzysztof Wilczyński
2024-10-09 15:00 ` Niklas Cassel
2024-10-10 2:17 ` Hongxing Zhu
2024-10-10 9:33 ` Niklas Cassel
2024-08-13 7:42 ` [PATCH v5 2/4] arm64: dts: imx8mq: Add dbi2 and atu reg for i.MX8MQ PCIe EP Richard Zhu
2024-08-13 8:54 ` Krzysztof Kozlowski
2024-08-13 8:55 ` Krzysztof Kozlowski
2024-08-13 7:42 ` [PATCH v5 3/4] arm64: dts: imx8mp: Add dbi2 and atu reg for i.MX8MP " Richard Zhu
2024-08-13 7:42 ` [PATCH v5 4/4] arm64: dts: imx8mm: Add dbi2 and atu reg for i.MX8MM " Richard Zhu
2024-08-31 13:02 ` [PATCH v5 0/4] Add dbi2 and atu for i.MX8M " Shawn Guo
2024-09-04 9:38 ` Shawn Guo
2024-09-09 1:43 ` Hongxing Zhu
2024-09-25 3:39 ` Hongxing Zhu
2024-09-25 3:45 ` Hongxing Zhu
2024-09-25 4:03 ` Hongxing Zhu
2024-10-08 8:30 ` Shawn Guo
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=ZtMTybL79ui5ocPM@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--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=robh@kernel.org \
--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).