From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Beau Belgrave <beaub@linux.microsoft.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-devel <linux-trace-devel@vger.kernel.org>,
bpf <bpf@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [PATCH v2] tracing: Set user_events to BROKEN
Date: Sun, 3 Apr 2022 10:39:33 -0400 [thread overview]
Message-ID: <20220403103933.787cc4de@rorschach.local.home> (raw)
In-Reply-To: <20220330155835.5e1f6669@gandalf.local.home>
On Wed, 30 Mar 2022 15:58:35 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> After being merged, user_events become more visible to a wider audience
> that have concerns with the current API. It is too late to fix this for
> this release, but instead of a full revert, just mark it as BROKEN (which
> prevents it from being selected in make config). Then we can work finding
> a better API. If that fails, then it will need to be completely reverted.
>
> Link: https://lore.kernel.org/all/2059213643.196683.1648499088753.JavaMail.zimbra@efficios.com/
>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Linus,
I noticed that you pulled in this patch (slightly updated subject). I
had it part of my queue that was going thought my tests, which have
just finished. I was going to send you a pull request today.
Is it OK that I keep that patch? Otherwise, I need to pull it out and
rerun my tests without it.
I would have had this to you earlier but because of the merge
conflicts of my last pull request that this queue depended on, I based
all my new changes off of the merge commit you had made with my
previous pull request, and that contained bugs that would prevent my
tests from passing (as you saw with the one memory mapping issue).
I'll go ahead and send you the pull request that I have that contains
this patch as well, but feel free to reject it if you want me to redo
my queue without it.
-- Steve
prev parent reply other threads:[~2022-04-03 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 19:58 [PATCH v2] tracing: Set user_events to BROKEN Steven Rostedt
2022-04-03 14:39 ` 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=20220403103933.787cc4de@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=beaub@linux.microsoft.com \
--cc=bpf@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 \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.