From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Mihai Sain <mihai.sain@microchip.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, nicolas.ferre@microchip.com,
cristian.birsan@microchip.com, alexandre.belloni@bootlin.com,
andre.przywara@arm.com, jerry.ray@microchip.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: andrei.simion@microchip.com, Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 1/2] dt-bindings: ARM: at91: Document Microchip SAMA5D29 Curiosity
Date: Mon, 25 Sep 2023 16:14:24 +0300 [thread overview]
Message-ID: <77b14fab-ea46-36bd-9886-49fc6cfc980e@tuxon.dev> (raw)
In-Reply-To: <20230919124606.26898-2-mihai.sain@microchip.com>
Hi, Mihai,
On 19.09.2023 15:46, Mihai Sain wrote:
> From: Andrei Simion <andrei.simion@microchip.com>
>
> Document device tree binding of SAMA5D29 Curiosity, from Microchip.
>
> Signed-off-by: Andrei Simion <andrei.simion@microchip.com>
Your SoB should have been here to reflect that this has been upstreamed by
you. Keep it in mind for next time. I adjusted it for now.
> Reviewed-by: Mihai Sain <mihai.sain@microchip.com>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
Applied to at91-dt, thanks!
next prev parent reply other threads:[~2023-09-25 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 12:46 [PATCH v4 0/2] Add initial support for SAMA5D29-Curiosity board Mihai Sain
2023-09-19 12:46 ` [PATCH v4 1/2] dt-bindings: ARM: at91: Document Microchip SAMA5D29 Curiosity Mihai Sain
2023-09-25 13:14 ` claudiu beznea [this message]
2023-09-19 12:46 ` [PATCH v4 2/2] ARM: dts: at91: sama5d29_curiosity: Add device tree for sama5d29_curiosity board Mihai Sain
2023-09-25 13:14 ` claudiu beznea
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=77b14fab-ea46-36bd-9886-49fc6cfc980e@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=andre.przywara@arm.com \
--cc=andrei.simion@microchip.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cristian.birsan@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jerry.ray@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.sain@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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).