From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shi Hao <i.shihao.999@gmail.com>
Cc: linusw@kernel.org, brgl@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, rric@kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: gpio: cavium,thunder-8890: Convert to DT schema
Date: Tue, 31 Mar 2026 09:30:56 +0200 [thread overview]
Message-ID: <20260331-invisible-certain-albatross-844cff@quoll> (raw)
In-Reply-To: <20260330080108.24294-1-i.shihao.999@gmail.com>
On Mon, Mar 30, 2026 at 01:31:08PM +0530, Shi Hao wrote:
> Convert Cavium ThunderX GPIO bindings to DT schema.
>
> Signed-off-by: Shi Hao <i.shihao.999@gmail.com>
> ---
>
> v2:
> - Rename schema file based on compatible string
> - Wrap commit message body as per kernel patch guidelines
> - Use appropriate maintainer name and email address in DT schema.
> - Change commit subject as per guidelines
> - Fix $id path
> - Rebased on linux-next
>
> Note:
> * This patch is part of the GSoC2026 application process for device tree bindings conversions
> * https://github.com/LinuxFoundationGSoC/ProjectIdeas/wiki/GSoC-2026-Device-Tree-Bindings
> ---
> .../gpio/cavium,thunder-8890-gpio.yaml | 45 +++++++++++++++++++
> .../bindings/gpio/gpio-thunderx.txt | 27 -----------
This binding is odd and not used, so you should follow guidelines I gave
more than a year ago and updated recently and NOT convert it.
Or rather answer - why this cannot be removed instead? What is the
benefit of this binding? Is any other project using it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-31 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 8:01 [PATCH v2] dt-bindings: gpio: cavium,thunder-8890: Convert to DT schema Shi Hao
2026-03-31 7:30 ` Krzysztof Kozlowski [this message]
2026-04-04 8:52 ` ShiHao
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=20260331-invisible-certain-albatross-844cff@quoll \
--to=krzk@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=i.shihao.999@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rric@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