From: Marek Vasut <marek.vasut@mailbox.org>
To: Matt Coster <Matt.Coster@imgtec.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
David Airlie <airlied@gmail.com>,
Frank Binns <Frank.Binns@imgtec.com>,
Alessio Belle <Alessio.Belle@imgtec.com>,
Alexandru Dadu <Alexandru.Dadu@imgtec.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>, Rob Herring <robh@kernel.org>,
Simona Vetter <simona@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: gpu: img,powervr-rogue: Drop duplicate newline
Date: Thu, 30 Oct 2025 14:51:22 +0100 [thread overview]
Message-ID: <bff8815c-e708-4573-a6f8-7fdec160a78f@mailbox.org> (raw)
In-Reply-To: <50c29b53-64b5-4ad4-a502-286248cbedfd@imgtec.com>
On 10/30/25 1:08 PM, Matt Coster wrote:
Hello Matt,
> On 29/10/2025 19:42, Marek Vasut wrote:
>> Fix the following DT schema check warning:
>>
>> ./Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml:103:1: [warning] too many blank lines (2 > 1) (empty-lines)
>>
>> One newline is enough. No functional change.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
>
> Good catch! Thanks for sending a fix. Does this also need:
Got a hint from Rob how to better scan bindings before sending patches,
so the credit really goes there.
> Fixes: 18ff1dc462ef ("dt-bindings: gpu: img,powervr-rogue: Document GX6250 GPU in Renesas R-Car M3-W/M3-W+")
I am not sure about this one, I would say no because it has no
functional impact on the kernel and/or does not fix any functional bug.
next prev parent reply other threads:[~2025-10-30 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 19:42 [PATCH] dt-bindings: gpu: img,powervr-rogue: Drop duplicate newline Marek Vasut
2025-10-29 22:07 ` Rob Herring (Arm)
2025-10-30 12:08 ` Matt Coster
2025-10-30 13:51 ` Marek Vasut [this message]
2025-10-31 14:42 ` Matt Coster
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=bff8815c-e708-4573-a6f8-7fdec160a78f@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=Alessio.Belle@imgtec.com \
--cc=Alexandru.Dadu@imgtec.com \
--cc=Frank.Binns@imgtec.com \
--cc=Matt.Coster@imgtec.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).