Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"moderated list:ARM/LPC32XX SOC SUPPORT"
	<linux-arm-kernel@lists.infradead.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	imx@lists.linux.dev
Subject: Re: [PATCH v2 5/5] ARM: dts: lpc3250-phy3250: remove deprecated at25* property
Date: Mon, 17 Nov 2025 11:12:37 -0500	[thread overview]
Message-ID: <aRtJdTMxFaXdVnvs@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <face044b-01ed-4077-b497-3caaccf57c98@mleia.com>

On Sat, Nov 15, 2025 at 02:23:50AM +0200, Vladimir Zapolskiy wrote:
> On 11/14/25 19:47, Frank Li wrote:
> > Remove duplicated deprecated at25* property because the same common
> > property already were added.
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> > changes in v2
> > - new patch
> > ---
> >   arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts | 4 ----
> >   1 file changed, 4 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts b/arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts
> > index 15463a96938cc..0f96ea0337a1f 100644
> > --- a/arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts
> > +++ b/arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts
> > @@ -213,10 +213,6 @@ eeprom: eeprom@0 {
> >   		pl022,wait-state = <0>;
> >   		pl022,duplex = <0>;
> > -		at25,byte-len = <0x8000>;
> > -		at25,addr-mode = <2>;
> > -		at25,page-size = <64>;
> > -
> >   		size = <0x8000>;
> >   		address-width = <16>;
> >   		pagesize = <64>;
>
> Just squash this change with the 3/5 from the series, or I can do it on
> patch application.

Yes, you can squash when apply.

Frank
>
> My ask about splitting the changes was about a separation of the 4/5 change,
> and it was done as expected, thank you.
>
> --
> Best wishes,
> Vladimir


  reply	other threads:[~2025-11-17 16:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 17:47 [PATCH v2 1/5] ARM: dts: lpc32xx: remove usb bus and elevate all children nodes Frank Li
2025-11-14 17:47 ` [PATCH v2 2/5] ARM: dts: lpc3250-ea3250: add key- prefix for gpio-keys Frank Li
2025-11-14 17:47 ` [PATCH v2 3/5] ARM: dts: lpc3250-phy3250: add at25 required properties Frank Li
2025-11-15  0:16   ` Vladimir Zapolskiy
2025-11-14 17:47 ` [PATCH v2 4/5] ARM: dts: lpc3250-phy3250: rename nodename at@0 to eeprom@0 Frank Li
2025-11-15  0:16   ` Vladimir Zapolskiy
2025-11-14 17:47 ` [PATCH v2 5/5] ARM: dts: lpc3250-phy3250: remove deprecated at25* property Frank Li
2025-11-15  0:23   ` Vladimir Zapolskiy
2025-11-17 16:12     ` Frank Li [this message]
2025-11-17 19:05       ` Vladimir Zapolskiy
2025-11-15  0:20 ` [PATCH v2 1/5] ARM: dts: lpc32xx: remove usb bus and elevate all children nodes Vladimir Zapolskiy

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=aRtJdTMxFaXdVnvs@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --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=piotr.wojtaszczyk@timesys.com \
    --cc=robh@kernel.org \
    --cc=vz@mleia.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