public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Akhila YS <akhilayalmati@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/5] dt-bindings: arm: microchip,sama7g5-chipid : convert to DT schema
Date: Tue, 24 Feb 2026 20:13:45 +0530	[thread overview]
Message-ID: <27eb620e-3924-4a78-ad31-0412e938e7e6@gmail.com> (raw)
In-Reply-To: <20260217-fleshy-giddily-80987f509638@spud>


On 17-02-2026 23:21, Conor Dooley wrote:
>  Akhila YS wrote:
>> Convert Atmel system registers binding to YAML format.
>>
>> Signed-off-by: Akhila YS <akhilayalmati@gmail.com>
>> ---
>>  .../bindings/arm/microchip,sama7g5-chipid.yaml     | 41 ++++++++++++++++++++++
>>  1 file changed, 41 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/microchip,sama7g5-chipid.yaml b/Documentation/devicetree/bindings/arm/microchip,sama7g5-chipid.yaml
>> new file mode 100644
>> index 000000000000..4227f308d43a
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/microchip,sama7g5-chipid.yaml
>> @@ -0,0 +1,41 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/arm/microchip,sama7g5-chipid.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Atmel/Microchip RAMC SDRAM/DDR Controller
>> +
>> +maintainers:
>> +  - Nicolas Ferre <nicolas.ferre@microchip.com>
>> +  - Claudiu Beznea <claudiu.beznea@microchip.com>
> This email no longer exists, think the new one is claudiu@tuxon.dev.
> Look it up in MAINTAINERS.


Sure.

-- 
Best Regards,
Akhila.



  reply	other threads:[~2026-02-24 14:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 17:24 [PATCH 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML Akhila YS
2026-02-17 17:24 ` [PATCH 1/5] dt-bindings: arm: microchip,sama7g5-chipid : convert to DT schema Akhila YS
2026-02-17 17:51   ` Conor Dooley
2026-02-24 14:43     ` Akhila YS [this message]
2026-02-17 17:24 ` [PATCH 2/5] dt-bindings: arm: atmel,at91sam9260-pit: " Akhila YS
2026-02-17 17:24 ` [PATCH 3/5] dt-bindings: arm: microchip,sam9x60-pit64b : " Akhila YS
2026-02-17 17:53   ` Conor Dooley
2026-02-24 14:44     ` Akhila YS
2026-02-17 17:24 ` [PATCH 4/5] dt-bindings: arm: atmel,at91rm9200-st: " Akhila YS
2026-02-17 17:24 ` [PATCH 5/5] dt-bindings: arm: atmel,at91rm9200-sdramc: " Akhila YS
2026-02-17 17:51 ` [PATCH 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML Conor Dooley
2026-02-24 14:42   ` Akhila YS
2026-02-24 14:56     ` Conor Dooley

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=27eb620e-3924-4a78-ad31-0412e938e7e6@gmail.com \
    --to=akhilayalmati@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --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