From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Shenwei Wang <shenwei.wang@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Peng Fan <peng.fan@nxp.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [EXT] Re: [PATCH v5 3/3] arm64: dts: imx: add imx8dxl support
Date: Tue, 9 Aug 2022 07:16:27 +0300 [thread overview]
Message-ID: <781cf213-0ca8-6b03-2d60-280bfeb6d39d@linaro.org> (raw)
In-Reply-To: <AM9PR04MB827446CA7B2887414A5C641C89639@AM9PR04MB8274.eurprd04.prod.outlook.com>
On 08/08/2022 21:16, Shenwei Wang wrote:
>> On 05/08/2022 18:22, Shenwei Wang wrote:
>>> A kind ping. 😊
>>>
>>>
>>
>> To whom? What do you need from me?
>>
>
> This the version 5 of the series of patches, and should have addressed all those comments from you and other reviewers. The other two commits were acked by you and Rob. This one hasn't gotten any feedback or ack so far. I would greatly appreciate it if you or Rob could ack it or let me know where to improve.
This is not a DT bindings patch. Why do you need or expect my ack?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-08-09 4:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 20:01 [PATCH v5 0/3] add imx8dxl evk support Shenwei Wang
2022-08-01 20:01 ` [PATCH v5 1/3] dt-bindings: firmware: add missing resource IDs for imx8dxl Shenwei Wang
2022-08-01 20:01 ` [PATCH v5 2/3] dt-bindings: arm: imx: update fsl.yaml " Shenwei Wang
2022-08-01 20:01 ` [PATCH v5 3/3] arm64: dts: imx: add imx8dxl support Shenwei Wang
2022-08-05 16:22 ` Shenwei Wang
2022-08-08 5:47 ` Krzysztof Kozlowski
2022-08-08 18:16 ` [EXT] " Shenwei Wang
2022-08-09 4:16 ` Krzysztof Kozlowski [this message]
2022-08-09 16:41 ` Shenwei Wang
2022-08-18 12:08 ` Shenwei Wang
2022-08-21 13:14 ` 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=781cf213-0ca8-6b03-2d60-280bfeb6d39d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-imx@nxp.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shenwei.wang@nxp.com \
/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).