From: Krzysztof Kozlowski <krzk@kernel.org>
To: Fabio Estevam <festevam@gmail.com>, neil.armstrong@linaro.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH] dt-bindings: display: panel-lvds: Add compatible for AUO G084SN05 V9
Date: Tue, 10 Dec 2024 08:16:12 +0100 [thread overview]
Message-ID: <6c2624c4-4835-48f4-a27c-81e570219292@kernel.org> (raw)
In-Reply-To: <20241209204003.1295503-1-festevam@gmail.com>
On 09/12/2024 21:40, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> The AUO G084SN05 V9 is a 8.4" 800x600 LVDS display.
>
> Add a compatible entry for this LVDS display model.
>
<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
</form letter>
Best regards,
Krzysztof
prev parent reply other threads:[~2024-12-10 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 20:40 [PATCH] dt-bindings: display: panel-lvds: Add compatible for AUO G084SN05 V9 Fabio Estevam
2024-12-09 20:40 ` [PATCH 2/2] arm64: dts: imx8mm-phg: Add LVDS compatible string Fabio Estevam
2024-12-10 7:16 ` Krzysztof Kozlowski [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=6c2624c4-4835-48f4-a27c-81e570219292@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=shawnguo@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