netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jakub Kicinski <kuba@kernel.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Karsten Keil <isdn@linux-pingi.de>, Arnd Bergmann <arnd@arndb.de>,
	isdn4linux@listserv.isdn4linux.de,
	netdev <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section
Date: Mon, 03 Feb 2020 03:07:01 -0800	[thread overview]
Message-ID: <ce81e9b1ac6ede9f7a16823175192ef69613ec07.camel@perches.com> (raw)
In-Reply-To: <CAHp75VdVXqz7fab4MKH2jZozx4NGGkQnJyTWHDKCdgSwD2AtpA@mail.gmail.com>

On Mon, 2020-02-03 at 12:13 +0200, Andy Shevchenko wrote:
> On Sun, Feb 2, 2020 at 10:45 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > On Sat,  1 Feb 2020 13:43:01 +0100, Lukas Bulwahn wrote:
> > > Commit 6d97985072dc ("isdn: move capi drivers to staging") cleaned up the
> > > isdn drivers and split the MAINTAINERS section for ISDN, but missed to add
> > > the terminal slash for the two directories mISDN and hardware. Hence, all
> > > files in those directories were not part of the new ISDN/mISDN SUBSYSTEM,
> > > but were considered to be part of "THE REST".
> > > 
> > > Rectify the situation, and while at it, also complete the section with two
> > > further build files that belong to that subsystem.
> > > 
> > > This was identified with a small script that finds all files belonging to
> > > "THE REST" according to the current MAINTAINERS file, and I investigated
> > > upon its output.
> > > 
> > > Fixes: 6d97985072dc ("isdn: move capi drivers to staging")
> > > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> > 
> > Applied to net, thanks!
> 
> I'm not sure it's ready. I think parse-maintainers.pl will change few
> lines here.

parse-maintainers would change a _lot_ of the MAINTAINERS file
by reordering section letters.

$ perl ./scripts/parse-maintainers.pl --output=MAINTAINERS
$ git diff --stat MAINTAINERS
 MAINTAINERS | 5572 +++++++++++++++++++++++++++++------------------------------
 1 file changed, 2786 insertions(+), 2786 deletions(-)



  reply	other threads:[~2020-02-03 11:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 12:43 [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section Lukas Bulwahn
2020-02-01 13:13 ` Arnd Bergmann
     [not found] ` <CAHp75Veb1fUkKyJ1_q=iXq=aFqtFrGoVMzoCk15CGaqmARUB+w@mail.gmail.com>
2020-02-01 14:46   ` Lukas Bulwahn
2020-02-01 18:32     ` Andy Shevchenko
2020-02-01 18:41 ` Joe Perches
2020-02-01 19:15   ` Lukas Bulwahn
2020-02-01 20:45     ` Joe Perches
2020-02-01 21:29       ` Lukas Bulwahn
2020-02-02 20:43 ` Jakub Kicinski
2020-02-03 10:13   ` Andy Shevchenko
2020-02-03 11:07     ` Joe Perches [this message]
2020-02-03 11:17       ` Andy Shevchenko
2020-02-04  5:08         ` Lukas Bulwahn
2020-02-04  5:35           ` Joe Perches
2020-02-03 17:35     ` Jakub Kicinski

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=ce81e9b1ac6ede9f7a16823175192ef69613ec07.camel@perches.com \
    --to=joe@perches.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=isdn4linux@listserv.isdn4linux.de \
    --cc=isdn@linux-pingi.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=netdev@vger.kernel.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).