From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Beau Belgrave <beaub@linux.microsoft.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-devel <linux-trace-devel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] tracing/user_events: Remove eBPF interfaces
Date: Tue, 29 Mar 2022 15:47:26 -0400 [thread overview]
Message-ID: <20220329154726.30c187df@gandalf.local.home> (raw)
In-Reply-To: <CAADnVQKG0LxsUMFGsFSEA4AqpSa8Kqg5HpUfKzPo9Ze463UDgw@mail.gmail.com>
On Tue, 29 Mar 2022 11:19:05 -0700
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> On Tue, Mar 29, 2022 at 10:30 AM Beau Belgrave
> <beaub@linux.microsoft.com> wrote:
> >
> > Remove eBPF interfaces within user_events to ensure they are fully
> > reviewed.
> >
> > Link: https://lore.kernel.org/all/20220329165718.GA10381@kbox/
> >
> > Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>
>
> Thanks for the quick revert.
>
> Steven,
>
> since you've applied the initial set please take this one and
> send pull req to Linus asap.
>
Relax Alexei,
I'll send it to Linus after it goes through my testing process with all my
other patches in queue. An ABI is only defined by the main release "5.18"
and not the rc releases (like 5.18-rc1). But it will definitely be gone
before rc2.
-- Steve
prev parent reply other threads:[~2022-03-29 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 17:30 [PATCH] tracing/user_events: Remove eBPF interfaces Beau Belgrave
2022-03-29 18:19 ` Alexei Starovoitov
2022-03-29 19:47 ` 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=20220329154726.30c187df@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.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).