From: Marek Vasut <marek.vasut@mailbox.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH] media: dt-bindings: raspberrypi,pispbe: Fix example indent
Date: Sun, 20 Sep 2026 19:17:09 +0200 [thread overview]
Message-ID: <797c63bc-b759-459c-99f2-d5c3146cbe67@mailbox.org> (raw)
In-Reply-To: <20260918-amusing-rat-of-nirvana-cda3f9@quoll>
On 9/18/26 12:44 PM, Krzysztof Kozlowski wrote:
> On Thu, Sep 17, 2026 at 02:25:18AM +0200, Marek Vasut wrote:
>> Fix two spaces before { in example. No functional change.
>>
>> DT checker reports this as follows:
>> "
>> ./Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml:56: example 0 [redundant-whitespace] extra whitespace before {
>
> I already posted this for more files:
> https://lore.kernel.org/all/20260801195528.235230-2-krzysztof.kozlowski@oss.qualcomm.com/
>
> And doing such changes file-per-file is quite a churn, so better to
> combine commits.
All right, please just apply yours, thanks !
I noticed it while running the DT checker, so I fixed it and sent a
patch, hence single file change.
prev parent reply other threads:[~2026-09-20 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 0:25 [PATCH] media: dt-bindings: raspberrypi,pispbe: Fix example indent Marek Vasut
2026-09-18 10:44 ` Krzysztof Kozlowski
2026-09-20 17:17 ` Marek Vasut [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=797c63bc-b759-459c-99f2-d5c3146cbe67@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel-list@raspberrypi.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@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