[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231115143410.e2c1ea567221d591b58ada1f@linux-foundation.org>
Date: Wed, 15 Nov 2023 14:34:10 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Joe Perches <joe@...ches.com>
Cc: Marco Elver <elver@...gle.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Paul Heidekrüger <paul.heidekrueger@....de>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kasan: default to inline instrumentation
On Tue, 14 Nov 2023 21:38:50 -0800 Joe Perches <joe@...ches.com> wrote:
> > +LIBRARY CODE
> > +M: Andrew Morton <akpm@...ux-foundation.org>
> > +L: linux-kernel@...r.kernel.org
> > +S: Supported
>
> Dunno.
>
> There are a lot of already specifically maintained or
> supported files in lib/
That's OK. I'll get printed out along with the existing list of
maintainers, if any.
> Maybe be a reviewer?
Would that alter the get_maintainer output in any way?
I suppose I could list each file individually, but I'm not sure what
that would gain.
btw, I see MAINTAINERS lists non-existent file[s] (lib/fw_table.c).
Maybe someone has a script to check...
Powered by blists - more mailing lists