From: Conor Dooley <conor@kernel.org>
To: Akhila YS <akhilayalmati@gmail.com>
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>,
Claudiu Beznea <claudiu@tuxon.dev>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML
Date: Tue, 24 Feb 2026 17:51:55 +0000 [thread overview]
Message-ID: <20260224-resisting-mongrel-531537974fa3@spud> (raw)
In-Reply-To: <20260224-recolor-hatching-e7d1b1894953@spud>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
On Tue, Feb 24, 2026 at 05:43:15PM +0000, Conor Dooley wrote:
> On Tue, Feb 24, 2026 at 02:46:45PM +0000, Akhila YS wrote:
> > Convert various legacy .txt bindings for Microchip (formerly Atmel) AT91/SAMA
> > family system peripherals to proper YAML schemas. This includes:
> >
> > - CHIPID (SoC ID register block)
> > - PIT (Period Interval Timer, old style)
> > - PIT64B (64-bit Period Interval Timer, newer parts)
> > - ST (System Timer, including watchdog subnode)
> > - RAMC/SDRAMC/DDRAMC/UDDRC (SDRAM/DDR memory controller
> >
> > Signed-off-by: Akhila YS <akhilayalmati@gmail.com>
> > ---
> > Changes in v2:
> > - Change email for maintainers.
> > - microchip,sam9x60-pit64b: modify compatible and clock-names in properties.
> > - Link to v1: https://lore.kernel.org/r/20260217-arm-microchip-v1-0-ae5d907e10e3@gmail.com
>
> Please give me a chance to respond to your messages before sending new
> versions. My comment about partial removal of the text file still
> applies. You've got to send another version anyway.
Also, you probably should have checked the what I thought was Claudiu's
email was actually correct. It's actually claudiu.beznea@tuxon.dev!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-24 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 14:46 [PATCH v2 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML Akhila YS
2026-02-24 14:46 ` [PATCH v2 1/5] dt-bindings: arm: microchip,sama7g5-chipid : convert to DT schema Akhila YS
2026-02-24 14:46 ` [PATCH v2 2/5] dt-bindings: arm: atmel,at91sam9260-pit: " Akhila YS
2026-02-24 14:46 ` [PATCH v2 3/5] dt-bindings: arm: microchip,sam9x60-pit64b : " Akhila YS
2026-02-24 14:46 ` [PATCH v2 4/5] dt-bindings: arm: atmel,at91rm9200-st: " Akhila YS
2026-02-24 16:59 ` Rob Herring (Arm)
2026-02-24 17:48 ` Conor Dooley
2026-02-25 15:10 ` Akhila YS
2026-02-24 14:46 ` [PATCH v2 5/5] dt-bindings: arm: atmel,at91rm9200-sdramc: " Akhila YS
2026-02-24 17:43 ` [PATCH v2 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML Conor Dooley
2026-02-24 17:51 ` Conor Dooley [this message]
2026-02-25 15:13 ` Akhila YS
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=20260224-resisting-mongrel-531537974fa3@spud \
--to=conor@kernel.org \
--cc=akhilayalmati@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=claudiu@tuxon.dev \
--cc=conor+dt@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