From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Sudeep Dutt <sudeep.dutt@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] MAINTAINERS: fix MIC maintainers entry
Date: Thu, 07 Jan 2016 01:59:53 -0800 [thread overview]
Message-ID: <1452160793.4028.13.camel@perches.com> (raw)
In-Reply-To: <20160107094345.GB5177@mwanda>
On Thu, 2016-01-07 at 12:43 +0300, Dan Carpenter wrote:
> I wrote some bash to find problems in MAINTAINERS. I'm not sure what to
> do with it.
>
> # Grep for missing colons
> for i in $(cut -b 1-2 MAINTAINERS | grep : | sort | uniq | cut -b 1) ; do
> egrep "^$i[ ]" MAINTAINERS
> done
>
> # Grep for non-existing files
> for i in $(grep ^F: MAINTAINERS | grep -v '\*' | cut -d : -f 2-) ; do
> if ! test -e $i ; then
> echo $i
> fi
> done
I run a similar script every once in awhile.
Here's my current list with -next:
$ verify_maintainer_patterns.pl
0 drivers/infiniband/hw/amso1100/
0 arch/arm/mach-pxa/include/mach/palmt5.h
0 arch/arm/mach-pxa/include/mach/palmte2.h
0 arch/arm/mach-pxa/include/mach/palmtreo.h
0 arch/arm/mach-pxa/include/mach/palmz72.h
0 arch/arm/plat-samsung/s5p-dev-mfc.c
0 include/media/atmel-isi.h
0 arch/mips/bcm3384/*
0 arch/mips/include/asm/mach-bcm3384/*
0 Documentation/cgroups/cpusets.txt
0 drivers/media/i2c/cs3308.h
0 include/media/cx2341x*
0 include/uapi/scsi/cxlflash_ioctls.h
0 Documentation/devicetree/bindings/drm/atmel/
0 Documentation/devicetree/bindings/display/panel/nec,nl4827hc19_05b.txt
0 include/drm/gma500*
0 drivers/infiniband/hw/ehca/
0 drivers/crypto/nx/nx_debugfs.h
0 Documentation/devicetree/bindings/i2c/ina209.txt
0 Documentation/s390/kvm.txt
0 drivers/scsi/mpt2sas/
0 drivers/hwmon/max20751.c
0 Documentation/devicetree/bindings/i2c/max6697.txt
0 include/media/saa7146*
0 drivers/staging/ft1000/
0 fs/hppfs/
prev parent reply other threads:[~2016-01-07 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 9:40 [patch] MAINTAINERS: fix MIC maintainers entry Dan Carpenter
2016-01-07 9:43 ` Dan Carpenter
2016-01-07 9:59 ` Joe Perches [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=1452160793.4028.13.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=ashutosh.dixit@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.dutt@intel.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