From: ShiHao <i.shihao.999@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: andi.shyti@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
conor+dt@kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
i.shihao.999@gmail.com
Subject: Re: [PATCH] dt-bindings: i2c: intel,ixp4xx-i2c: Convert to Dt schema
Date: Sat, 28 Mar 2026 15:16:49 +0530 [thread overview]
Message-ID: <acejiSOOcHmqcouI@fedora> (raw)
In-Reply-To: <1bda00e6-a3bf-4890-8982-4d61a4b4845e@kernel.org>
On Thu, Mar 26, 2026 at 08:08:06AM +0100, Krzysztof Kozlowski wrote:
> By running, I assume actually read its output and fix it, so please
> share why each one of your patches has the same mistake reported by
> checkpatch?
>
> > I will send the next version in the coming days after properly running the
> > checkpatch.pl script. Also, you mentioned some guidelines regarding GSoC
> > could you please let me know where I can read them?
>
> I gave them to GSoC folks, so they should be in the GSoC DT
> guidelines/description. It was also posted for more than a year on
> @krzk@social.kernel.org and some days ago I updated it as well.
>
> Best regards,
> Krzysztof
Hello Krzysztof,
I hope you are doing good. I checked this binding it has 3 warnings
one of them was from the license text and the rest two are this"
WARNING: DT binding docs and includes should be a separate patch.
See: Documentation/devicetree/bindings/submitting-patches.rst". I fixed
the license warning but not these two "DT binding doc warnings". I wonder
what warning you want me to fix please let me know if i need to solve
this remaining two warnings because they are in my every conversion patches.
Thanks
Shihao
prev parent reply other threads:[~2026-03-28 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 13:50 [PATCH] dt-bindings: i2c: intel,ixp4xx-i2c: Convert to Dt schema Shi Hao
2026-03-25 11:16 ` Krzysztof Kozlowski
2026-03-25 15:10 ` ShiHao
2026-03-25 15:15 ` Krzysztof Kozlowski
2026-03-25 18:31 ` ShiHao
2026-03-26 7:08 ` Krzysztof Kozlowski
2026-03-28 9:46 ` ShiHao [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=acejiSOOcHmqcouI@fedora \
--to=i.shihao.999@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-i2c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.