From: "james qian wang (Arm Technology China)" <james.qian.wang@arm.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Brian Starkey <Brian.Starkey@arm.com>,
Joe Perches <joe@perches.com>, Daniel Vetter <daniel@ffwll.ch>,
DRI-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>, nd <nd@arm.com>
Subject: Re: [PATCH] MAINTAINERS: Fix pattern for Documentation path for Arm Mali Komeda
Date: Wed, 27 Mar 2019 06:21:54 +0000 [thread overview]
Message-ID: <20190327062147.GA8455@james-ThinkStation-P300> (raw)
In-Reply-To: <20190326103203.8891-1-Liviu.Dudau@arm.com>
On Tue, Mar 26, 2019 at 10:32:03AM +0000, Liviu Dudau wrote:
> The Device Tree bindings documentation file is in a simplified path
> that doesn't match the MAINTAINERS entry.
>
> Reported-by: Joe Perches <joe@perches.com>
> Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e17ebf70b5480..9fa4686212bdd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1167,7 +1167,7 @@ S: Supported
> T: git git://linux-arm.org/linux-ld.git for-upstream/mali-dp
> F: drivers/gpu/drm/arm/display/include/
> F: drivers/gpu/drm/arm/display/komeda/
> -F: Documentation/devicetree/bindings/display/arm/arm,komeda.txt
> +F: Documentation/devicetree/bindings/display/arm,komeda.txt
> F: Documentation/gpu/komeda-kms.rst
>
> ARM MALI-DP DRM DRIVER
> --
> 2.21.0
--
Thank you for fixing this problem.
Reviewed-by: James Qian Wang (Arm Technology China) <james.qian.wang@arm.com>
prev parent reply other threads:[~2019-03-27 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190325233040.30983-1-joe@perches.com>
2019-03-26 10:32 ` [PATCH] MAINTAINERS: Fix pattern for Documentation path for Arm Mali Komeda Liviu Dudau
2019-03-27 6:21 ` james qian wang (Arm Technology China) [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=20190327062147.GA8455@james-ThinkStation-P300 \
--to=james.qian.wang@arm.com \
--cc=Brian.Starkey@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nd@arm.com \
/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