From: Meng Li <Meng.Li@windriver.com>
To: linux@roeck-us.net, s.hauer@pengutronix.de,
kernel@pengutronix.de, linux-watchdog@vger.kernel.org,
imx@lists.linux.dev, shawnguo@kernel.org, robh@kernel.org,
conor+dt@kernel.org, Frank.Li@nxp.com
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, meng.li@windriver.com
Subject: [v4 PATCH 0/2] create patches for nxp-ls1046a platform watchdog feature
Date: Wed, 4 Jun 2025 11:42:44 +0800 [thread overview]
Message-ID: <20250604034246.3234837-1-Meng.Li@windriver.com> (raw)
v4:
- Improve commit log of patch0002
v3:
- merge patch 0002 into patch 0001
- improve the commit log of patches
v2:
- improve the commit log of patch 0001
- add another 2 patches to fix below warning
arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dtb: watchdog@2ad0000(fsl,imx21-wdt): big-endian: False schema does not allow True
v1:
- create patch 0001-arch-arm64-dts-add-big-endian-property-back-into-wat.patch
Meng Li (2):
dt-bindings: watchdog: fsl-imx-wdt: add compatible string
fsl,ls1046a-wdt
arch: arm64: dts: add big-endian property back into watchdog node
Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.yaml | 2 ++
arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 3 ++-
2 files changed, 4 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2025-06-04 3:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 3:42 Meng Li [this message]
2025-06-04 3:42 ` [v4 PATCH 1/2] dt-bindings: watchdog: fsl-imx-wdt: add compatible string fsl,ls1046a-wdt Meng Li
2025-06-05 17:40 ` Rob Herring
2025-06-06 1:44 ` Li, Meng
2025-06-06 1:48 ` Li, Meng
2025-06-04 3:42 ` [v4 PATCH 2/2] arch: arm64: dts: add big-endian property back into watchdog node Meng Li
2025-06-06 1:46 ` [v4 PATCH 0/2] create patches for nxp-ls1046a platform watchdog feature Li, Meng
2025-06-06 15:34 ` Frank Li
2025-06-08 3:08 ` Li, Meng
-- strict thread matches above, loose matches on Subject: below --
2025-06-08 3:06 Meng Li
2025-06-18 12:43 ` Li, Meng
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=20250604034246.3234837-1-Meng.Li@windriver.com \
--to=meng.li@windriver.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).