linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH Y.A. RESEND] MAINTAINERS: fix alpha. ordering
Date: Sun, 23 Jul 2017 13:10:09 -0700	[thread overview]
Message-ID: <1500840609.23924.3.camel@perches.com> (raw)
In-Reply-To: <CA+55aFybQDR32wVo9heNme+aRFjUV7h3P8B1F4MxC7J=T4u+zA@mail.gmail.com>

On Sun, 2017-07-23 at 13:00 -0700, Linus Torvalds wrote:
> it looks like there were four copies of "GREYBUS PROTOCOLS
> DRIVERS". WTF? I didn't check if there was something else odd going
> on.
> 
> I guess they'd need to be made unique somehow too.

right.

Unfortunate about the duplicate section headers.

get_maintainers doesn't care what the section headers are
but your script does.  

Easy fix though prior to running the script.

$ grep -P "^[0-9A-Za-z][^:]" MAINTAINERS|sort|uniq -c | sort -rn
      4 GREYBUS PROTOCOLS DRIVERS
      2 SYNC FILE FRAMEWORK
      2 NOKIA N900 CAMERA SUPPORT (ET8EK8 SENSOR, AD5820 FOCUS)

  reply	other threads:[~2017-07-23 20:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 20:32 [PATCH Y.A. RESEND] MAINTAINERS: fix alpha. ordering Randy Dunlap
2017-07-22  2:01 ` Linus Torvalds
2017-07-23 19:49 ` Linus Torvalds
2017-07-23 20:00   ` Linus Torvalds
2017-07-23 20:10     ` Joe Perches [this message]
2017-07-23 23:14     ` Linus Torvalds
2017-07-24  1:38       ` Joe Perches
2017-07-28  0:30       ` Joe Perches
2017-07-28  2:43         ` Linus Torvalds
2017-07-28  3:12           ` Joe Perches
2017-07-28 22:30             ` Linus Torvalds
2017-07-29  1:08               ` Joe Perches
2017-07-29 17:46               ` Joe Perches
2017-07-23 20:05   ` Joe Perches

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=1500840609.23924.3.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).