From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ryan.Wanner@microchip.com, lgirdwood@gmail.com,
broonie@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@microchip.com
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] dt-bindings: sound: Convert to json-schema
Date: Tue, 12 Jul 2022 10:09:00 +0200 [thread overview]
Message-ID: <b2934014-8048-6c17-e655-bd1be09794bc@linaro.org> (raw)
In-Reply-To: <20220711183010.39123-1-Ryan.Wanner@microchip.com>
On 11/07/2022 20:30, Ryan.Wanner@microchip.com wrote:
> From: Ryan Wanner <Ryan.Wanner@microchip.com>
>
> This patch series converts atmel-classd and atmel-pdmic device tree
> bindings to json-schema.
>
> v1 -> v2:
> - Fix commit formatting.
> - Fix titles in yaml file
> - Removed trivial descriptions
> - Correct formatting errors
>
> Ryan Wanner (2):
> dt-bindings: sound: atmel,classd: Convert to json-schema
> dt-binding: sound: atmel,pdmic: Convert to json-schema
Use consistent and proper prefix. I think you got such comment before,
right?
Best regards,
Krzysztof
prev parent reply other threads:[~2022-07-12 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 18:30 [PATCH v2 0/2] dt-bindings: sound: Convert to json-schema Ryan.Wanner
2022-07-11 18:30 ` [PATCH v2 1/2] dt-bindings: sound: atmel,classd: " Ryan.Wanner
2022-07-12 8:12 ` Krzysztof Kozlowski
2022-07-12 8:14 ` Krzysztof Kozlowski
2022-07-11 18:30 ` [PATCH v2 2/2] dt-binding: sound: atmel,pdmic: " Ryan.Wanner
2022-07-12 8:14 ` Krzysztof Kozlowski
2022-07-11 18:35 ` [PATCH v2 0/2] dt-bindings: sound: " Conor.Dooley
2022-07-12 8:09 ` Krzysztof Kozlowski [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=b2934014-8048-6c17-e655-bd1be09794bc@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Ryan.Wanner@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).