From: <Sergiu.Moga@microchip.com>
To: <Nicolas.Ferre@microchip.com>, <krzysztof.kozlowski@linaro.org>,
<broonie@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<Tudor.Ambarus@microchip.com>
Cc: <linux-spi@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <Claudiu.Beznea@microchip.com>,
<alexandre.belloni@bootlin.com>,
<Kavyasree.Kotagiri@microchip.com>,
<UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH] dt-bindings: spi: convert spi_atmel to json-schema
Date: Thu, 30 Jun 2022 06:07:54 +0000 [thread overview]
Message-ID: <2bbea8cc-6f17-6236-6f4b-352a274784de@microchip.com> (raw)
In-Reply-To: <f641fd0e-2da2-112e-f2fb-f5d89af00587@microchip.com>
On 29.06.2022 18:01, Nicolas Ferre wrote:
> Sergiu,
>
> On 29/06/2022 at 15:23, Krzysztof Kozlowski wrote:
>>> +title: Atmel SPI device
>>> +
>>> +maintainers:
>>> + - Mark Brown<broonie@kernel.org>
>> This should be rather someone from Microchip.
>
> Tudor Ambarus <tudor.ambarus@microchip.com> is our maintainer for SPI
> controller, sorry for not having advised you internally about this ;-)
>
> Best regards,
> Nicolas
>
Noted. Thank you, Nicolas :).
Regards,
Sergiu
next prev parent reply other threads:[~2022-06-30 6:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 12:58 [PATCH] dt-bindings: spi: convert spi_atmel to json-schema Sergiu Moga
2022-06-29 13:23 ` Krzysztof Kozlowski
2022-06-29 15:01 ` Nicolas Ferre
2022-06-30 6:07 ` Sergiu.Moga [this message]
2022-06-30 5:59 ` Sergiu.Moga
2022-06-29 14:12 ` Mark Brown
2022-06-29 22:36 ` Rob Herring
2022-06-29 22:45 ` Conor.Dooley
2022-06-30 21:12 ` Rob Herring
2022-06-30 22:22 ` Conor.Dooley
2022-07-01 7:41 ` Nicolas Ferre
2022-07-01 7:50 ` Conor.Dooley
2022-07-01 7:56 ` Nicolas Ferre
2022-06-30 6:05 ` Sergiu.Moga
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=2bbea8cc-6f17-6236-6f4b-352a274784de@microchip.com \
--to=sergiu.moga@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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).