From: Benjamin GAIGNARD <benjamin.gaignard@st.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>, Rob Herring <robh@kernel.org>
Cc: Lucas Stach <l.stach@pengutronix.de>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>, Joe Perches <joe@perches.com>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: adjust to VIVANTE GPU schema conversion
Date: Mon, 16 Mar 2020 08:05:07 +0000 [thread overview]
Message-ID: <18450dfa-a150-45df-5b9c-c543c110c478@st.com> (raw)
In-Reply-To: <20200315072109.6815-1-lukas.bulwahn@gmail.com>
On 3/15/20 8:21 AM, Lukas Bulwahn wrote:
> Commit 90aeca875f8a ("dt-bindings: display: Convert etnaviv to
> json-schema") missed to adjust the DRM DRIVERS FOR VIVANTE GPU IP entry
> in MAINTAINERS.
>
> Since then, ./scripts/get_maintainer.pl --self-test complains:
>
> warning: no file matches \
> F: Documentation/devicetree/bindings/display/etnaviv/
>
> Update MAINTAINERS entry to location of converted schema.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Reviewed-by: Benjamin Gaignard <benjamin.gaignard@st.com>
Thanks
> ---
> applies cleanly on next-20200313
>
> Benjamin, please ack.
> Rob, please pick this patch (it is not urgent, though)
>
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 77eede976d0f..50a7a6d62e06 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5766,7 +5766,7 @@ L: dri-devel@lists.freedesktop.org
> S: Maintained
> F: drivers/gpu/drm/etnaviv/
> F: include/uapi/drm/etnaviv_drm.h
> -F: Documentation/devicetree/bindings/display/etnaviv/
> +F: Documentation/devicetree/bindings/gpu/vivante,gc.yaml
>
> DRM DRIVERS FOR ZTE ZX
> M: Shawn Guo <shawnguo@kernel.org>
prev parent reply other threads:[~2020-03-16 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 7:21 Lukas Bulwahn
2020-03-16 8:05 ` Benjamin GAIGNARD [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=18450dfa-a150-45df-5b9c-c543c110c478@st.com \
--to=benjamin.gaignard@st.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--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
all inboxes | Powered by JetHome®