public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: nicolas.ferre@microchip.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Balamanikandan Gunasundar
	<balamanikandan.gunasundar@microchip.com>,
	Ryan Wanner <ryan.wanner@microchip.com>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH 0/5] ARM: dts: microchip: sama7d65: flexcom nodes upgrade
Date: Fri, 9 Jan 2026 08:58:16 +0200	[thread overview]
Message-ID: <2c3bebff-41ca-49f2-a8bd-e51d630ee7fc@tuxon.dev> (raw)
In-Reply-To: <20260102170135.70717-1-nicolas.ferre@microchip.com>



On 1/2/26 19:01, nicolas.ferre@microchip.com wrote:
> Hari Prasath Gujulan Elango (1):
>    ARM: dts: microchip: sama7d65: fix the ranges property for flx9
> 
> Nicolas Ferre (4):
>    ARM: dts: microchip: sama7d65: fix size-cells property for i2c3

Applied to at91-fixes, thanks!

>    ARM: dts: microchip: sama7d65: add dma properties to usart6
>    ARM: dts: microchip: sama7d65: add fifo-size to usart
>    ARM: dts: microchip: sama7d65: add missing flexcom nodes

Applied to at91-dt, thanks!


      parent reply	other threads:[~2026-01-09  6:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 17:01 [PATCH 0/5] ARM: dts: microchip: sama7d65: flexcom nodes upgrade nicolas.ferre
2026-01-02 17:01 ` [PATCH 1/5] ARM: dts: microchip: sama7d65: fix the ranges property for flx9 nicolas.ferre
2026-01-02 17:01 ` [PATCH 2/5] ARM: dts: microchip: sama7d65: fix size-cells property for i2c3 nicolas.ferre
2026-01-02 17:01 ` [PATCH 3/5] ARM: dts: microchip: sama7d65: add dma properties to usart6 nicolas.ferre
2026-01-02 17:01 ` [PATCH 4/5] ARM: dts: microchip: sama7d65: add fifo-size to usart nicolas.ferre
2026-01-02 17:01 ` [PATCH 5/5] ARM: dts: microchip: sama7d65: add missing flexcom nodes nicolas.ferre
2026-01-09  6:58 ` claudiu beznea [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=2c3bebff-41ca-49f2-a8bd-e51d630ee7fc@tuxon.dev \
    --to=claudiu.beznea@tuxon.dev \
    --cc=alexandre.belloni@bootlin.com \
    --cc=balamanikandan.gunasundar@microchip.com \
    --cc=conor.dooley@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=ryan.wanner@microchip.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