From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: robh@kernel.org, wsa+renesas@sang-engineering.com,
dri-devel@lists.freedesktop.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next] dt-bindings: net: Use consistent indentation in the example
Date: Mon, 14 Sep 2026 17:50:27 +0200 [thread overview]
Message-ID: <c4eb78c2-ec82-4246-9050-74c59acf0615@oss.qualcomm.com> (raw)
In-Reply-To: <20260914123106.44CC81F000FF@smtp.kernel.org>
On 14/09/2026 14:31, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The `mdio0` block containing the `phy0` and `phy1` node definitions was accidentally deleted during indentation cleanup, resulting in unresolved phandle references.
> --
>
> commit 3067fd6538b78515dc2a63a2028de505854e6496
> Author: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
> dt-bindings: net: Use consistent indentation in the example
>
> This patch corrects the indentation in various device tree binding examples
> to conform to a consistent 2- or 4-space indent style. It aims to resolve
> dt-check-style warnings across multiple net and wireless bindings files.
That was intentional, just forgot to write in the commit msg.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-14 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 12:29 [PATCH net-next] dt-bindings: net: Use consistent indentation in the example Krzysztof Kozlowski
2026-09-14 9:14 ` Claudiu Manoil
2026-09-14 9:17 ` Krzysztof Kozlowski
2026-09-14 12:31 ` sashiko-bot
2026-09-14 15:50 ` Krzysztof Kozlowski [this message]
2026-09-14 12:50 ` netdev-bot+sashiko
2026-09-14 15:52 ` 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=c4eb78c2-ec82-4246-9050-74c59acf0615@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.com \
/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