From: patchwork-bot+netdevbpf@kernel.org
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com,
beaub@linux.microsoft.com, mhiramat@kernel.org,
linux-trace-devel@vger.kernel.org, bpf@vger.kernel.org,
netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
torvalds@linux-foundation.org, michal.lkml@markovi.net,
ndesaulniers@google.com, linux-kbuild@vger.kernel.org,
masahiroy@kernel.org
Subject: Re: [PATCH] tracing: Move user_events.h temporarily out of include/uapi
Date: Tue, 05 Apr 2022 16:20:48 +0000 [thread overview]
Message-ID: <164917564862.18481.12734568923836492201.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220401143903.188384f3@gandalf.local.home>
Hello:
This patch was applied to netdev/net-next.git (master)
by Steven Rostedt (Google) <rostedt@goodmis.org>:
On Fri, 1 Apr 2022 14:39:03 -0400 you wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> While user_events API is under development and has been marked for broken
> to not let the API become fixed, move the header file out of the uapi
> directory. This is to prevent it from being installed, then later changed,
> and then have an old distro user space update with a new kernel, where
> applications see the user_events being available, but the old header is in
> place, and then they get compiled incorrectly.
>
> [...]
Here is the summary with links:
- tracing: Move user_events.h temporarily out of include/uapi
https://git.kernel.org/netdev/net-next/c/5cfff569cab8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-04-06 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 18:39 [PATCH] tracing: Move user_events.h temporarily out of include/uapi Steven Rostedt
2022-04-05 16:20 ` patchwork-bot+netdevbpf [this message]
2022-04-05 16:32 ` Steven Rostedt
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=164917564862.18481.12734568923836492201.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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 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).