[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69ed8a468b3e4776d277292a2e4b2f9b3c266f23.camel@perches.com>
Date: Mon, 09 Mar 2020 16:12:24 -0700
From: Joe Perches <joe@...ches.com>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Guenter Roeck <groeck@...gle.com>,
Stephen Boyd <swboyd@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
Julius Werner <jwerner@...omium.org>,
kernel-janitors@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] MAINTAINERS: include GOOGLE FIRMWARE entry
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.
Powered by blists - more mailing lists