From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Balakrishnan Sambath <balakrishnan.s@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Linus Walleij <linus.walleij@linaro.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: dts: microchip: sama5d2: Move pinfunc.h headers
Date: Thu, 29 Feb 2024 18:43:13 +0100 [thread overview]
Message-ID: <5d6d78b6-28e2-40a1-80f8-4a9748a4b25e@linaro.org> (raw)
In-Reply-To: <20240229-pio4-pinctrl-yaml-v1-1-c4d8279c083f@microchip.com>
On 29/02/2024 12:39, Balakrishnan Sambath wrote:
> Move sama5d2-pinfunc.h into include/dt-bindings/pinctrl so that we can
> include it in yaml dt-binding examples.
That is not a the reason to make something a binding. Please provide
rationale why this is supposed to be binding. Because it does not look
like at all and it is kind of contradictory to what we recently were
doing - moving from bindings to DTS.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-02-29 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 11:39 [PATCH 0/3] convert Atmel's PIO4 bindings to json-schema Balakrishnan Sambath
2024-02-29 11:39 ` [PATCH 1/3] ARM: dts: microchip: sama5d2: Move pinfunc.h headers Balakrishnan Sambath
2024-02-29 17:43 ` Krzysztof Kozlowski [this message]
2024-02-29 11:39 ` [PATCH 2/3] ARM: dts: microchip: sama7g5: " Balakrishnan Sambath
2024-02-29 17:43 ` Krzysztof Kozlowski
2024-02-29 11:39 ` [PATCH 3/3] dt-bindings: pinctrl: at91-pio4: convert Atmel's PIO4 bindings to json-schema Balakrishnan Sambath
2024-02-29 12:45 ` Rob Herring
2024-02-29 17:41 ` Krzysztof Kozlowski
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=5d6d78b6-28e2-40a1-80f8-4a9748a4b25e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=balakrishnan.s@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.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).