From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: "Marco Elver" <elver@google.com>,
"Andrey Konovalov" <andreyknvl@gmail.com>,
"Paul Heidekrüger" <paul.heidekrueger@tum.de>,
"Andrey Ryabinin" <ryabinin.a.a@gmail.com>,
"Alexander Potapenko" <glider@google.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kasan: default to inline instrumentation
Date: Wed, 15 Nov 2023 14:34:10 -0800 [thread overview]
Message-ID: <20231115143410.e2c1ea567221d591b58ada1f@linux-foundation.org> (raw)
In-Reply-To: <918c3ff64f352427731104c5275786c815b860d9.camel@perches.com>
On Tue, 14 Nov 2023 21:38:50 -0800 Joe Perches <joe@perches.com> wrote:
> > +LIBRARY CODE
> > +M: Andrew Morton <akpm@linux-foundation.org>
> > +L: linux-kernel@vger.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...
next prev parent reply other threads:[~2023-11-15 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 15:51 Paul Heidekrüger
2023-11-09 21:08 ` Andrey Konovalov
2023-11-14 11:00 ` Marco Elver
2023-11-14 23:11 ` Andrew Morton
2023-11-15 5:38 ` Joe Perches
2023-11-15 8:26 ` Marco Elver
2023-11-15 22:34 ` Andrew Morton [this message]
2023-11-15 22:48 ` Joe Perches
2023-11-15 22:51 ` Andrew Morton
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=20231115143410.e2c1ea567221d591b58ada1f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=joe@perches.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.heidekrueger@tum.de \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.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®