From: Rob Herring <robh@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel@vger.kernel.org, malidp@foss.arm.com,
Liviu Dudau <liviu.dudau@arm.com>,
kernel-janitors@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Brian Starkey <brian.starkey@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
James Wang <james.qian.wang@arm.com>,
Mihail Atanassov <mihail.atanassov@arm.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] MAINTAINERS: rectify entries for ARM DRM DRIVERS after dt conversion
Date: Mon, 6 Jun 2022 12:18:55 -0500 [thread overview]
Message-ID: <20220606171855.GA912412-robh@kernel.org> (raw)
In-Reply-To: <20220601041746.22986-1-lukas.bulwahn@gmail.com>
On Wed, 01 Jun 2022 06:17:46 +0200, Lukas Bulwahn wrote:
> The three commits:
>
> 36fd2a65bcaf ("dt-bindings: display: convert Arm HDLCD to DT schema")
> 0f6983509ea1 ("dt-bindings: display: convert Arm Komeda to DT schema")
> 2c8b082a3ab1 ("dt-bindings: display: convert Arm Mali-DP to DT schema")
>
> convert the arm display dt-bindings, arm,*.txt to arm,*.yaml, but miss to
> adjust its reference in MAINTAINERS.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about
> broken references.
>
> Repair these file references in ARM HDLCD DRM DRIVER, ARM KOMEDA DRM-KMS
> DRIVER and ARM MALI-DP DRM DRIVER.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Andre, please ack.
> Rob, Krzysztof, please pick this minor non-urgent clean-up patch in
> your -next dt tree.
>
> MAINTAINERS | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2022-06-06 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 4:17 [PATCH] MAINTAINERS: rectify entries for ARM DRM DRIVERS after dt conversion Lukas Bulwahn
2022-06-01 8:47 ` Andre Przywara
2022-06-06 17:18 ` Rob Herring [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=20220606171855.GA912412-robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=andre.przywara@arm.com \
--cc=brian.starkey@arm.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.qian.wang@arm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lukas.bulwahn@gmail.com \
--cc=malidp@foss.arm.com \
--cc=mihail.atanassov@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).