From: Dinh Nguyen <dinguyen@kernel.org>
To: evon.chiam@altera.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: altera: move all SoCFPGA device trees from dts/intel
Date: Tue, 8 Sep 2026 05:18:21 -0500 [thread overview]
Message-ID: <114057e1-f35b-4ca4-ae8f-dd2fd66180b3@kernel.org> (raw)
In-Reply-To: <802bf0d27fbff9b1ddb6b9fc323a1a9f8f050f74.1788512748.git.evon.chiam@altera.com>
On 9/4/26 18:06, evon.chiam@altera.com wrote:
> From: "Chiam, Evon" <evon.chiam@altera.com>
>
> The dts/intel/ directory contains two distinct families:
> - Altera SoCFPGA platforms (Stratix 10, Agilex, Agilex5, Agilex72,
> Agilex7M, N5X)
> - Intel Keembay
>
Nit: replace "device trees" in your commit header with either "support"
or "files" . The "dts" in the header is already saying these are changes
to device trees.
Also replace "from dts/intel" to "to dts/altera".
Dinh
next prev parent reply other threads:[~2026-09-08 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 10:06 evon.chiam
2026-09-08 10:18 ` Dinh Nguyen [this message]
2026-09-09 7:19 ` Chiam, Evon
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=114057e1-f35b-4ca4-ae8f-dd2fd66180b3@kernel.org \
--to=dinguyen@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=evon.chiam@altera.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®