From: Joe Perches <joe@perches.com>
To: "Duda, Sebastian" <sebastian.duda@fau.de>
Cc: linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com,
ralf.ramsauer@oth-regensburg.de,
wolfgang.mauerer@oth-regensburg.de
Subject: Re: get_maintainers.pl subsystem output
Date: Fri, 19 Jul 2019 07:31:16 -0700 [thread overview]
Message-ID: <dc45dc9c8af1f1a2073de5c49283ba3cf3a0a2f0.camel@perches.com> (raw)
In-Reply-To: <6fa4aa44f343616459b17054197d0a22@fau.de>
On Fri, 2019-07-19 at 09:54 +0000, Duda, Sebastian wrote:
> On 2019-07-19 08:50, Joe Perches wrote:
> > > My Questions are:
> > > 1. How can I make get_maintainer's output to be more table-like?
> >
> > I suggest adding --nogit --nogit-fallback --roles --norolestats
>
> Unfortunately, this doesn't change the output:
> $ scripts/get_maintainer.pl --subsystem --status --separator ,
> drivers/media/i2c/adv748x/
> Kieran Bingham <kieran.bingham@ideasonboard.com> (maintainer:ANALOG
> DEVICES INC ADV748X DRIVER),Mauro Carvalho Chehab <mchehab@kernel.org>
> (maintainer:MEDIA INPUT INFRASTRUCTURE
> (V4L/DVB)),linux-media@vger.kernel.org (open list:ANALOG DEVICES INC
> ADV748X DRIVER),linux-kernel@vger.kernel.org (open list)
> Maintained,Buried alive in reporters
> ANALOG DEVICES INC ADV748X DRIVER,MEDIA INPUT INFRASTRUCTURE
> (V4L/DVB),THE REST
It does change the output for files that do not
have a specific maintainer.
> > > 2. How can I make get_maintainer.pl to separate each file's output?
> >
> > Run the script with multiple invocations. once for each file
> > modified by the patch.
>
> This is the way I'm doing it right now but this is very slow. I thought
> calling the script only once for many files could speed up the analysis.
get_maintainer is effectively single threaded.
Averaging 10 runs:
A single file run time is ~0.135 seconds on my system.
An invocation with two files on the command line has
a run time of ~0.195 seconds.
Using something like gnu parallel would allow multiple
instances to run simulateously and would significantly
reduce overall wall-clock runtime on most systems.
https://www.gnu.org/software/parallel/
next prev parent reply other threads:[~2019-07-19 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 7:35 Duda, Sebastian
2019-07-19 8:50 ` Joe Perches
2019-07-19 9:54 ` Duda, Sebastian
2019-07-19 14:31 ` Joe Perches [this message]
2019-07-23 7:29 ` Duda, Sebastian
2019-07-23 8:42 ` Lukas Bulwahn
2019-07-23 11:18 ` Joe Perches
2019-07-23 13:25 ` Lukas Bulwahn
2019-07-23 13:33 ` Joe Perches
2019-07-23 11:54 ` 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=dc45dc9c8af1f1a2073de5c49283ba3cf3a0a2f0.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=sebastian.duda@fau.de \
--cc=wolfgang.mauerer@oth-regensburg.de \
/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
all inboxes | Powered by JetHome®