From: patchwork-bot+netdevbpf@kernel.org
To: Artem Savkov <asavkov@redhat.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org, rostedt@goodmis.org,
mhiramat@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, tglx@linutronix.de,
linux-rt-users@vger.kernel.org, jolsa@kernel.org
Subject: Re: [PATCH bpf-next] bpf: change syscall_nr type to int in struct syscall_tp_t
Date: Fri, 13 Oct 2023 19:50:23 +0000 [thread overview]
Message-ID: <169722662338.10738.1648512697831961767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231013054219.172920-1-asavkov@redhat.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 13 Oct 2023 07:42:19 +0200 you wrote:
> linux-rt-devel tree contains a patch (b1773eac3f29c ("sched: Add support
> for lazy preemption")) that adds an extra member to struct trace_entry.
> This causes the offset of args field in struct trace_event_raw_sys_enter
> be different from the one in struct syscall_trace_enter:
>
> struct trace_event_raw_sys_enter {
> struct trace_entry ent; /* 0 12 */
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: change syscall_nr type to int in struct syscall_tp_t
https://git.kernel.org/bpf/bpf-next/c/ba8ea72388a1
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:[~2023-10-13 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 13:52 [RFC PATCH] tracing: change syscall number type in struct syscall_trace_* Artem Savkov
2023-10-03 22:11 ` Andrii Nakryiko
2023-10-04 7:02 ` Artem Savkov
2023-10-04 1:38 ` Steven Rostedt
2023-10-04 12:55 ` Artem Savkov
2023-10-05 12:34 ` Artem Savkov
2023-10-12 11:45 ` [RFC PATCH bpf-next] bpf: change syscall_nr type to int in struct syscall_tp_t Artem Savkov
2023-10-12 13:44 ` Steven Rostedt
2023-10-12 23:32 ` Andrii Nakryiko
2023-10-13 5:42 ` [PATCH " Artem Savkov
2023-10-13 19:50 ` patchwork-bot+netdevbpf [this message]
2023-10-13 6:01 ` [RFC PATCH " Artem Savkov
2023-10-13 14:00 ` Steven Rostedt
2023-10-13 19:43 ` Andrii Nakryiko
2023-10-16 15:53 ` Steven Rostedt
2023-10-13 3:13 ` Rod Webster
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=169722662338.10738.1648512697831961767.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=asavkov@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).