From: Shawn Guo <shawnguo@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/9] accumulated dts updates for ls1046a
Date: Sun, 23 Oct 2022 21:24:48 +0800 [thread overview]
Message-ID: <20221023132448.GQ125525@dragon> (raw)
In-Reply-To: <20220922214030.9004-1-leoyang.li@nxp.com>
On Thu, Sep 22, 2022 at 04:40:21PM -0500, Li Yang wrote:
> v2 updates:
> - Style fixes
> - Updated to use MACROs for interrupt and gpio property
> - Remove dma-coherent for remaining nodes under SoC
>
> v3 updates:
> - Added dma-noncoherent exception for edma
I probably forgot to reply, but v2 of the series has landed on v6.1-rc1.
So please send updates against v6.1-rc1.
Shawn
prev parent reply other threads:[~2022-10-23 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 21:40 [PATCH v3 0/9] accumulated dts updates for ls1046a Li Yang
2022-09-22 21:40 ` [PATCH v3 1/9] arm64: dts: ls1046a: Enable usb3-lpm-capable for usb3 node Li Yang
2022-09-22 21:40 ` [PATCH v3 2/9] arm64: dts: ls1046a: Add the PME interrupt and big-endian to PCIe EP nodes Li Yang
2022-09-22 21:40 ` [PATCH v3 3/9] arm64: dts: ls1046a: Add big-endian property for PCIe nodes Li Yang
2022-09-22 21:40 ` [PATCH v3 4/9] arm64: dts: ls1046a: add missing dma ranges property Li Yang
2022-09-22 21:40 ` [PATCH v3 5/9] arm64: dts: ls1046a: make dma-coherent global to the SoC Li Yang
2022-09-22 21:40 ` [PATCH v3 6/9] arm64: dts: ls1046a: use a pseudo-bus to constrain usb and sata dma size Li Yang
2022-09-22 21:40 ` [PATCH v3 7/9] arm64: dts: ls1046a: add gpios based i2c recovery information Li Yang
2022-09-22 21:40 ` [PATCH v3 8/9] arm64: dts: ls1046a-qds: add mmio based mdio-mux nodes for FPGA Li Yang
2022-09-22 21:40 ` [PATCH v3 9/9] arm64: dts: ls1046a-qds: Modify the qspi flash frequency Li Yang
2022-10-23 13:24 ` Shawn Guo [this message]
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=20221023132448.GQ125525@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).