From: Mark Brown <broonie@kernel.org>
To: Sergiu Moga <sergiu.moga@microchip.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
claudiu.beznea@microchip.com, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Kavyasree.Kotagiri@microchip.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH] dt-bindings: spi: convert spi_atmel to json-schema
Date: Wed, 29 Jun 2022 15:12:53 +0100 [thread overview]
Message-ID: <Yrxd5X+HukjXMsFM@sirena.org.uk> (raw)
In-Reply-To: <20220629125804.137099-1-sergiu.moga@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
On Wed, Jun 29, 2022 at 03:58:04PM +0300, Sergiu Moga wrote:
> Convert SPI binding for Atmel/Microchip SoCs to Device Tree Schema
> format.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-29 14:13 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
2022-06-30 5:59 ` Sergiu.Moga
2022-06-29 14:12 ` Mark Brown [this message]
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=Yrxd5X+HukjXMsFM@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=sergiu.moga@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