From: Joe Perches <joe@perches.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Guenter Roeck <groeck@google.com>,
Stephen Boyd <swboyd@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Julius Werner <jwerner@chromium.org>,
kernel-janitors@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] MAINTAINERS: include GOOGLE FIRMWARE entry
Date: Mon, 09 Mar 2020 16:12:24 -0700 [thread overview]
Message-ID: <69ed8a468b3e4776d277292a2e4b2f9b3c266f23.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2003092035300.2953@felia>
On Mon, 2020-03-09 at 22:03 +0100, Lukas Bulwahn wrote:
> I am starting with the "bigger" clustered files in drivers, and then try
> > > to look at files in include and Documentation/ABI/.
If you want to spend the time tracking stuff down,
it may be best to to
start with include/
> > > Here is a rough statistics on how many files from each directory are in
> > > THE REST:
> > >
> > > 1368 include
There are very likely some files there that should
actually be listed as part of a subsystem.
> > > 327 lib
Not many that aren't trivial or ancient.
> > > 321 Documentation
Probably a few
> > > 100 drivers
What's not already maintained is probably ancient.
Everything else may not matter much.
next prev parent reply other threads:[~2020-03-09 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 19:51 Lukas Bulwahn
2020-03-08 19:57 ` Greg Kroah-Hartman
2020-03-08 20:13 ` Joe Perches
2020-03-08 22:32 ` Guenter Roeck
2020-03-08 22:54 ` Joe Perches
2020-03-09 6:32 ` Lukas Bulwahn
2020-03-09 7:05 ` Greg Kroah-Hartman
2020-03-09 21:03 ` Lukas Bulwahn
2020-03-09 23:12 ` Joe Perches [this message]
2020-03-10 6:48 ` Lukas Bulwahn
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=69ed8a468b3e4776d277292a2e4b2f9b3c266f23.camel@perches.com \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=groeck@google.com \
--cc=jwerner@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®