linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Bad file pattern in MAINTAINERS section 'ARM/UNIPHIER ARCHITECTURE'
Date: Tue, 26 Mar 2019 10:58:49 +0530	[thread overview]
Message-ID: <20190326052849.GV5348@vkoul-mobl> (raw)
In-Reply-To: <20190325212453.25934-1-joe@perches.com>

On 25-03-19, 14:24, Joe Perches wrote:
> A file pattern line in this section of the MAINTAINERS file in linux-next
> does not have a match in the linux source files.
> 
> This could occur because a matching filename was never added, was deleted
> or renamed in some other commit.
> 
> The commits that added and if found renamed or removed the file pattern
> are shown below.
> 
> Please fix this defect appropriately.
> 
> 1: ---------------------------------------------------------------------------
> 
> linux-next MAINTAINERS section:
> 
> 	2344	ARM/UNIPHIER ARCHITECTURE
> 	2345	M:	Masahiro Yamada <yamada.masahiro@socionext.com>
> 	2346	L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> 	2347	T:	git git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier.git
> 	2348	S:	Maintained
> 	2349	F:	Documentation/devicetree/bindings/arm/socionext/uniphier.txt
> 	2350	F:	Documentation/devicetree/bindings/gpio/gpio-uniphier.txt
> 	2351	F:	Documentation/devicetree/bindings/pinctrl/socionext,uniphier-pinctrl.txt
> 	2352	F:	arch/arm/boot/dts/uniphier*
> 	2353	F:	arch/arm/include/asm/hardware/cache-uniphier.h
> 	2354	F:	arch/arm/mach-uniphier/
> 	2355	F:	arch/arm/mm/cache-uniphier.c
> 	2356	F:	arch/arm64/boot/dts/socionext/uniphier*
> 	2357	F:	drivers/bus/uniphier-system-bus.c
> 	2358	F:	drivers/clk/uniphier/
> -->	2359	F:	drivers/dmaengine/uniphier-mdmac.c

yeah this should be drivers/dma/<>

I have fixed it up with below

 --8<--


From: Vinod Koul <vkoul@kernel.org>
Date: Tue, 26 Mar 2019 10:55:47 +0530
Subject: [PATCH] MAINTAINERS: Fix uniphier-mdmac.c file path

Commit 32e74aabebc8 ("dmaengine: uniphier-mdmac: add UniPhier MIO DMAC
driver") wrongly put filepath for uniphier-mdmac.c, fix it

Fixes: 32e74aabebc8 ("dmaengine: uniphier-mdmac: add UniPhier MIO DMAC driver")
Reported-by: Joe Perches <joe@perches.com>
Signed-off-by: Vinod Koul <vkoul@kernel.org>
---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index e17ebf70b548..67e895feddc8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2356,7 +2356,7 @@ F:	arch/arm/mm/cache-uniphier.c
 F:	arch/arm64/boot/dts/socionext/uniphier*
 F:	drivers/bus/uniphier-system-bus.c
 F:	drivers/clk/uniphier/
-F:	drivers/dmaengine/uniphier-mdmac.c
+F:	drivers/dma/uniphier-mdmac.c
 F:	drivers/gpio/gpio-uniphier.c
 F:	drivers/i2c/busses/i2c-uniphier*
 F:	drivers/irqchip/irq-uniphier-aidet.c
-- 
2.20.1

Thanks
-- 
~Vinod

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-03-26  5:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-03-25 21:24 ` Bad file pattern in MAINTAINERS section 'ARM INTEGRATOR, VERSATILE AND REALVIEW SUPPORT' Joe Perches
2019-08-13  6:10   ` [PATCH] MAINTAINERS: Update path to physmap-versatile.c Denis Efremov
2019-08-13  6:32     ` [RESEND PATCH] " Denis Efremov
2019-08-13  7:20       ` Linus Walleij
2019-09-10 11:46         ` Denis Efremov
2019-09-30 20:48     ` [RESEND v2 " Denis Efremov
2019-03-25 21:24 ` Bad file pattern in MAINTAINERS section 'ARM/UNIPHIER ARCHITECTURE' Joe Perches
2019-03-26  5:28   ` Vinod Koul [this message]
2019-08-13  6:10 ` [PATCH] MAINTAINERS: Update path to tcb_clksrc.c Denis Efremov
2019-08-13  8:11   ` Nicolas.Ferre
2019-08-14  9:08     ` Alexandre Belloni
2019-08-23  8:20       ` Nicolas.Ferre

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=20190326052849.GV5348@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=joe@perches.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).