From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH v1] MAINTAINERS: Sort entries in database for VSPRINTF
Date: Mon, 10 Feb 2020 16:51:29 +0200 [thread overview]
Message-ID: <20200210145129.GV10400@smile.fi.intel.com> (raw)
In-Reply-To: <20200210142154.x2azckvduvh3xuea@pathway.suse.cz>
On Mon, Feb 10, 2020 at 03:21:55PM +0100, Petr Mladek wrote:
> Hi Andy,
>
> On Tue 2020-01-28 16:34:25, Andy Shevchenko wrote:
> > Run parse-maintainers.pl and choose VSPRINTF record. Fix it accordingly.
>
> Does this produce any visible error or warning anywhere, please?
Not for the moment.
Nevertheless, there is an initial motivation behind this [1,2].
> checkpatch.pl does not warn about it.
>
> Also the order does not look defined in the file. When I run
> parse-maintainers.pl on the entire MAINTAINERS file:
See [2] for the details.
> MAINTAINERS | 5584 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------------------------------------------
> 1 file changed, 2787 insertions(+), 2797 deletions(-)
>
> The file has 18545 lines. It means that huge amount of entries
> do not follow the order.
Yes, but it's getting better.
[1]: 7683e9e52925 ("Properly alphabetize MAINTAINERS file")
[2]: https://lore.kernel.org/lkml/CA+55aFy3naVgbRubhjfq7k4CcSiFOEdQNkNwHTLDLmepECu9yA@mail.gmail.com/
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-02-10 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 14:34 Andy Shevchenko
2020-02-10 14:21 ` Petr Mladek
2020-02-10 14:51 ` Andy Shevchenko [this message]
2020-02-10 14:53 ` Andy Shevchenko
2020-02-11 11:45 ` Petr Mladek
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=20200210145129.GV10400@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@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
all inboxes | Powered by JetHome®