From: patchwork-bot+netdevbpf@kernel.org
To: Denys Zagorui <dzagorui@cisco.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] samples: bpf: fix syscall_tp openat argument
Date: Mon, 23 Oct 2023 17:10:22 +0000 [thread overview]
Message-ID: <169808102264.23259.3811927107836817360.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231019113521.4103825-1-dzagorui@cisco.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 19 Oct 2023 04:35:21 -0700 you wrote:
> This modification doesn't change behaviour of the syscall_tp
> But such code is often used as a reference so it should be
> correct anyway
>
> Signed-off-by: Denys Zagorui <dzagorui@cisco.com>
> ---
> samples/bpf/syscall_tp_kern.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
Here is the summary with links:
- samples: bpf: fix syscall_tp openat argument
https://git.kernel.org/bpf/bpf-next/c/69a19170303f
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-23 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 11:35 [PATCH] samples: bpf: fix syscall_tp openat argument Denys Zagorui
2023-10-23 17:10 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-19 11:23 Denys Zagorui
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=169808102264.23259.3811927107836817360.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dzagorui@cisco.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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).