From: Vladimir Zapolskiy <vz@mleia.com>
To: Frank Li <Frank.li@nxp.com>, Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/11] ARM: dts: nxp: clean lpc18xx DTB check warning
Date: Thu, 4 Sep 2025 16:35:43 +0300 [thread overview]
Message-ID: <147ba109-684e-4490-887a-54f7efae1d03@mleia.com> (raw)
In-Reply-To: <aKiCIZf0eG2F0nvr@lizhi-Precision-Tower-5810>
Hi Frank,
On 8/22/25 17:43, Frank Li wrote:
> On Sun, Jul 06, 2025 at 02:46:56PM -0400, Frank Li via B4 Relay wrote:
>> There are 3 dt-binding patch wait for pick.
>> [1] https://lore.kernel.org/imx/20250617-hound-of-improbable-intensity-e7c3c9@kuoka/
>> [2] https://lore.kernel.org/imx/174916907717.3619367.3745642154654809311.robh@kernel.org/
>> [3] https://lore.kernel.org/imx/175087864578.2055525.4510390315154712025.robh@kernel.org/
>>
>> lpc18xx related DTB warnings reduce to 0.
>
> Vladimir Zapolskiy and arnd:
>
> I asked shawn, these are not owned by him.
>
> who will pickup these patches?
I'll do it.
I'm preparing a few more changes for LPC32xx also, and I will send a PR for v6.18.
--
Best wishes,
Vladimir
prev parent reply other threads:[~2025-09-04 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 18:46 [PATCH 00/11] ARM: dts: nxp: clean lpc18xx DTB check warning Frank Li via B4 Relay
2025-07-06 18:46 ` [PATCH 01/11] ARM: dts: lpc18xx: rename node name flash-controller to spi Frank Li via B4 Relay
2025-07-06 18:46 ` [PATCH 02/11] ARM: dts: lpc18xx: rename node name mmcsd to mmc Frank Li via B4 Relay
2025-07-06 18:46 ` [PATCH 03/11] ARM: dts: lpc4350-hitex-eval: change node name flash to flash@0 Frank Li via B4 Relay
2025-07-06 18:47 ` [PATCH 04/11] ARM: dts: lpc18xx: swap clock-names bic and cui Frank Li via B4 Relay
2025-07-06 18:47 ` [PATCH 05/11] ARM: dts: lpc: add #address-cells and #size-cells for sram node Frank Li via B4 Relay
2025-07-06 18:47 ` [PATCH 06/11] ARM: dts: lpc: add cfg surfix in pinctrl child node Frank Li via B4 Relay
2025-07-06 18:47 ` [PATCH 07/11] ARM: dts: lpc4357-myd-lpc4357: add power-supply for innolux,at070tn92 Frank Li via B4 Relay
2025-07-06 18:47 ` [PATCH 08/11] ARM: dts: lpc: change node name 'button[0-9]' to button-[0-9]' Frank Li via B4 Relay
2025-07-06 18:47 ` [PATCH 09/11] ARM: dts: lpc4357-myd-lpc4357: change node name mdio0 to mdio Frank Li via B4 Relay
2025-07-06 18:47 ` [PATCH 10/11] ARM: dts: lpc18xx: add #address-cell and #szie-cell for spi flash controller Frank Li via B4 Relay
2025-07-06 18:47 ` [PATCH 11/11] ARM: dts: lpc18xx: add missed arm,num-irq-priority-bits Frank Li via B4 Relay
2025-08-22 14:43 ` [PATCH 00/11] ARM: dts: nxp: clean lpc18xx DTB check warning Frank Li
2025-09-04 13:35 ` Vladimir Zapolskiy [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=147ba109-684e-4490-887a-54f7efae1d03@mleia.com \
--to=vz@mleia.com \
--cc=Frank.li@nxp.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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