public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
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,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: gpio: convert Cavium ThunderX GPIO binding to YAML
Date: Tue, 10 Mar 2026 10:41:53 +0100	[thread overview]
Message-ID: <ac0fce9b-8fd3-42fe-8819-60be3132823e@kernel.org> (raw)
In-Reply-To: <20260310-snobbish-white-caterpillar-e8ef29@quoll>

On 10/03/2026 10:40, Krzysztof Kozlowski wrote:
> On Mon, Mar 09, 2026 at 01:52:52PM +0530, Shi Hao wrote:
>> Convert Cavium ThunderX GPIO text based device tree
>> node to YAML schema format, ensuring validation and
>> consistency across Device Tree.
> 
> Please wrap commit message according to Linux coding style / submission
> process (neither too early nor over the limit):
> https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
> 
> Is this part of some LFX/GSoC program and thus should be first reviewed
> by your mentors?

I see GSoC:
https://lore.kernel.org/all/aapjuiq0JSVWfmWA@fedora/

so which mentors reviewed this patch?

One more thing - subject: there is no YAML here. Please read submitting
patches in DT dir.

Best regards,
Krzysztof

  reply	other threads:[~2026-03-10  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  8:22 [PATCH] dt-bindings: gpio: convert Cavium ThunderX GPIO binding to YAML Shi Hao
2026-03-10  9:40 ` Krzysztof Kozlowski
2026-03-10  9:41   ` Krzysztof Kozlowski [this message]
2026-03-25 11:21 ` 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=ac0fce9b-8fd3-42fe-8819-60be3132823e@kernel.org \
    --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 \
    /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