From: Rob Herring <robh@kernel.org>
To: "Chiam, Evon" <evon.chiam@altera.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Lothar Rubusch <l.rubusch@gmail.com>,
Ng Tze Yee <tzeyee.ng@altera.com>,
Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>,
Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>,
Brian Masney <bmasney@redhat.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: arm: altera: fix Agilex72 compatible vendor prefix
Date: Fri, 14 Aug 2026 12:35:51 -0500 [thread overview]
Message-ID: <20260814173551.GC1981719-robh@kernel.org> (raw)
In-Reply-To: <b027b8cf-a97b-4670-a57c-1585feccb21e@altera.com>
On Fri, Aug 14, 2026 at 04:18:59PM +0800, Chiam, Evon wrote:
>
>
> On 12/8/2026 10:49 am, Rob Herring wrote:
> > On Thu, Aug 06, 2026 at 05:25:01PM +0800, evon.chiam@altera.com wrote:
> > > From: "Chiam, Evon" <evon.chiam@altera.com>
> > >
> > > Altera has separated from Intel. Update the Agilex72 SoC and board
> > > compatible strings to use the Altera vendor prefix instead of intel.
> >
> > Sorry, without better reasoning, you are stuck with them as sashiko
> > pointed out.
> >
> Sashiko’s comment on the DTS still using the intel compatible strings was
> based on reviewing patch 1/5 alone. Patch 4/5 moves the Agilex72 DT from
> arch/arm64/boot/dts/intel/ to arch/arm64/boot/dts/altera/ and updates the
> compatible strings to altr. With both patches applied, the bindings and DTS
> remain consistent.
>
> Would you prefer that I combine the patches 1/5 and 4/5 into a single patch
> so the binding and DTS updates land together?
Moving the dts directory is fine (though that is really up to SoC
maintainers). Changing compatible strings is not. It is not about the
patch split. It is an ABI. There are exceptions though. Generally that
is if there is no one with the h/w or the current .dts is so incomplete
that anyone using the h/w will need to update their DTB anyways.
Rob
next prev parent reply other threads:[~2026-08-14 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 9:25 [PATCH 0/5] clk: socfpga: add Agilex72 clock manager support evon.chiam
2026-08-06 9:25 ` [PATCH 1/5] dt-bindings: arm: altera: fix Agilex72 compatible vendor prefix evon.chiam
2026-08-12 2:49 ` Rob Herring
2026-08-14 8:18 ` Chiam, Evon
2026-08-14 17:35 ` Rob Herring [this message]
2026-08-06 9:25 ` [PATCH 2/5] dt-bindings: clock: altr,agilex72-clkmgr: add Agilex72 clock manager binding evon.chiam
2026-08-06 9:25 ` [PATCH 3/5] clk: socfpga: agilex72: add clock manager driver for Agilex72 evon.chiam
2026-08-10 17:42 ` Brian Masney
2026-08-06 9:25 ` [PATCH 4/5] arm64: dts: altera: move Agilex72 DT and use altr prefix evon.chiam
2026-08-06 9:25 ` [PATCH 5/5] arm64: dts: altera: agilex72: add clock manager support evon.chiam
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=20260814173551.GC1981719-robh@kernel.org \
--to=robh@kernel.org \
--cc=adrian.ho.yin.ng@altera.com \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=evon.chiam@altera.com \
--cc=krzk+dt@kernel.org \
--cc=l.rubusch@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=sboyd@kernel.org \
--cc=tzeyee.ng@altera.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