devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm: altera: combine Intel's SoCFPGA into altera.yaml
Date: Fri, 12 Dec 2025 06:21:41 -0600	[thread overview]
Message-ID: <7c750ad3-9d93-48e6-b546-719f6f13d446@kernel.org> (raw)
In-Reply-To: <20251211135613.GA898633-robh@kernel.org>



On 12/11/25 07:56, Rob Herring wrote:
> On Wed, Dec 10, 2025 at 10:33:53PM -0600, Dinh Nguyen wrote:
>> For all SoCFPGA platforms, whether it has the "intel" or "altr" vendor
>> prefix are referring to the same business unit that is responsible for
>> the platform. And now that Altera has spun off to be a separate corporate
>> entity from Intel, it would make sense to have the device bindings
>> documentation in the same file.
>>
>> Move the Intel AgileX board binding documentations into the same file that
>> contains the Altera ones.
>>
>> Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
>> ---
>>   .../devicetree/bindings/arm/altera.yaml       | 26 ++++++++++++
>>   .../bindings/arm/intel,socfpga.yaml           | 40 -------------------
>>   2 files changed, 26 insertions(+), 40 deletions(-)
>>   delete mode 100644 Documentation/devicetree/bindings/arm/intel,socfpga.yaml
> 
> I'm assuming you will take this via soc tree. Let me know if you want me
> to take it.
> 

Yes, I'll take it via the soc tree.

Thanks,
Dinh


      reply	other threads:[~2025-12-12 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11  4:33 [PATCH] dt-bindings: arm: altera: combine Intel's SoCFPGA into altera.yaml Dinh Nguyen
2025-12-11  4:57 ` Krzysztof Kozlowski
2025-12-11 13:56 ` Rob Herring
2025-12-12 12:21   ` Dinh Nguyen [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=7c750ad3-9d93-48e6-b546-719f6f13d446@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).