From: Steven Rostedt <rostedt@goodmis.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
dcook@linux.microsoft.com, alanau@linux.microsoft.com,
brauner@kernel.org, akpm@linux-foundation.org,
linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 00/11] tracing/user_events: Remote write ABI
Date: Tue, 21 Feb 2023 14:35:35 -0500 [thread overview]
Message-ID: <20230221143535.3207b6ee@gandalf.local.home> (raw)
In-Reply-To: <20230221174251.GA1786@kbox>
On Tue, 21 Feb 2023 09:42:51 -0800
Beau Belgrave <beaub@linux.microsoft.com> wrote:
> Would you prefer I start another version and include the key maintainers
> from fs/exec.c, kernel/exit.c, and kernel/fork.c?
Yeah, you could just do a "[RESEND]" patch set, if nothing has changed (or
maybe just rebase if needed.
>
> I've added akpm and brauner in these patches. I've pinged akpm privately
> about these, but didn't get any responses.
Yeah, I think he'd rather see what others think before doing anything.
>
> It seems like Eric Biederman, Kees Cook, and linux-mm would be good
> folks to add here from get_maintainers outputs.
Sure. And yes, definitely include linux-mm.
-- Steve
prev parent reply other threads:[~2023-02-21 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 23:05 [PATCH v7 00/11] tracing/user_events: Remote write ABI Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 01/11] tracing/user_events: Split header into uapi and kernel Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 02/11] tracing/user_events: Track fork/exec/exit for mm lifetime Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 03/11] tracing/user_events: Use remote writes for event enablement Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 04/11] tracing/user_events: Fixup enable faults asyncly Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 05/11] tracing/user_events: Add ioctl for disabling addresses Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 06/11] tracing/user_events: Update self-tests to write ABI Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 07/11] tracing/user_events: Add ABI self-test Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 08/11] tracing/user_events: Use write ABI in example Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 09/11] tracing/user_events: Update documentation for ABI Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 10/11] tracing/user_events: Charge event allocs to cgroups Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 11/11] tracing/user_events: Limit global user_event count Beau Belgrave
2023-02-20 22:01 ` [PATCH v7 00/11] tracing/user_events: Remote write ABI Steven Rostedt
2023-02-21 17:42 ` Beau Belgrave
2023-02-21 19:35 ` Steven Rostedt [this message]
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=20230221143535.3207b6ee@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=alanau@linux.microsoft.com \
--cc=beaub@linux.microsoft.com \
--cc=brauner@kernel.org \
--cc=dcook@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.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;
as well as URLs for NNTP newsgroup(s).