linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	avi.fishman@nuvoton.com, davem@davemloft.net,
	gregkh@linuxfoundation.org, rdunlap@infradead.org,
	avifishman70@gmail.com, tmaimon77@gmail.com,
	linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org
Subject: Re: [PATCH v2 1/1] MAINTAINERS: add subfolders for nuvoton *npcm*
Date: Mon, 2 Jul 2018 19:28:17 -0300	[thread overview]
Message-ID: <20180702192610.291e885e@coco.lan> (raw)
In-Reply-To: <578ce3d69b43c580d5e810741364b4d86174c3f0.camel@perches.com>

Em Mon, 02 Jul 2018 14:58:00 -0700
Joe Perches <joe@perches.com> escreveu:

> On Mon, 2018-07-02 at 14:45 -0700, Andrew Morton wrote:
> > On Sun,  1 Jul 2018 12:30:28 +0300 avi.fishman@nuvoton.com wrote:
> >   
> > > From: Avi Fishman <AviFishman70@gmail.com>
> > > 
> > > Add several subfolders to look for *npcm* files under
> > > ARM/NUVOTON NPCM ARCHITECTURE
> > > 
> > > Signed-off-by: Avi Fishman <AviFishman70@gmail.com>
> > > ---
> > >  MAINTAINERS | 3 +++
> > >  1 file changed, 3 insertions(+)
> > > 
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index e0ce3c5f32e5..23c450adad44 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -1727,7 +1727,10 @@ F:	arch/arm/mach-npcm/
> > >  F:	arch/arm/boot/dts/nuvoton-npcm*
> > >  F:	include/dt-bindings/clock/nuvoton,npcm7xx-clks.h
> > >  F:	drivers/*/*npcm*
> > > +F:	drivers/*/*/*npcm*
> > >  F:	Documentation/*/*npcm*
> > > +F:	Documentation/*/*/*npcm*
> > > +F:	Documentation/*/*/*/*npcm*  
> > 
> > The Docuemntation/ pathnames have changed.  Please refresh to the
> > current Linus tree.  
> 
> $ git ls-files Documentation | grep npcm
> Documentation/devicetree/bindings/arm/cpu-enable-method/nuvoton,npcm750-smp
> Documentation/devicetree/bindings/arm/npcm/npcm.txt
> Documentation/devicetree/bindings/clock/nuvoton,npcm750-clk.txt
> Documentation/devicetree/bindings/ipmi/npcm7xx-kcs-bmc.txt
> Documentation/devicetree/bindings/timer/nuvoton,npcm7xx-timer.txt
> Documentation/devicetree/bindings/usb/npcm7xx-usb.txt
> Documentation/devicetree/bindings/watchdog/nuvoton,npcm-wdt.txt
> 
> So maybe:
> 
> F:	Documentation/devicetree/bindings/*/*npcm*
> F:	Documentation/devicetree/bindings/*/*/*npcm*
> 

It is already like that, since commit
	5efa6f8473cc ("MAINTAINERS: fix location of DT npcm files")

Btw, I suggest to check documentation references with:

	./scripts/documentation-file-ref-check

It helps to identify if the links are pointing to the right
places. It does it tree-wide, though, and not per patch.

Thanks,
Mauro

      reply	other threads:[~2018-07-02 22:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01  9:30 [PATCH v2 0/1] MAINTAINERS: add subfolders for nuvoton *npcm* avi.fishman
2018-07-01  9:30 ` [PATCH v2 1/1] " avi.fishman
2018-07-02 21:45   ` Andrew Morton
2018-07-02 21:58     ` Joe Perches
2018-07-02 22:28       ` Mauro Carvalho Chehab [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=20180702192610.291e885e@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=avi.fishman@nuvoton.com \
    --cc=avifishman70@gmail.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rdunlap@infradead.org \
    --cc=tmaimon77@gmail.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).