From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
sdf@google.com, haoluo@google.com, revest@chromium.org
Subject: Re: [PATCHv3 bpf-next 0/3] bpf: Get rid of trace_printk_lock
Date: Mon, 19 Dec 2022 21:10:18 +0000 [thread overview]
Message-ID: <167148421882.25912.2818674096499754269.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221215214430.1336195-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 15 Dec 2022 22:44:27 +0100 you wrote:
> hi,
> In the last revision Andrii suggested we could have the buffer
> provided by bpf_bprintf_prepare [1]. It's bit more changes but
> it looks like more compact solution.
>
> v3 changes:
> - added struct to hold return data in bpf_bprintf_prepare
> - fix bug in bpf_bprintf_cleanup
> - adjust printk helpers to use new bpf_bprintf_prepare
> data argument
>
> [...]
Here is the summary with links:
- [PATCHv3,bpf-next,1/3] bpf: Add struct for bin_args arg in bpf_bprintf_prepare
https://git.kernel.org/bpf/bpf-next/c/78aa1cc94043
- [PATCHv3,bpf-next,2/3] bpf: Do cleanup in bpf_bprintf_cleanup only when needed
https://git.kernel.org/bpf/bpf-next/c/f19a4050455a
- [PATCHv3,bpf-next,3/3] bpf: Remove trace_printk_lock
https://git.kernel.org/bpf/bpf-next/c/e2bb9e01d589
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-19 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 21:44 [PATCHv3 bpf-next 0/3] bpf: Get rid of trace_printk_lock Jiri Olsa
2022-12-15 21:44 ` [PATCHv3 bpf-next 1/3] bpf: Add struct for bin_args arg in bpf_bprintf_prepare Jiri Olsa
2022-12-17 0:25 ` Yonghong Song
2022-12-15 21:44 ` [PATCHv3 bpf-next 2/3] bpf: Do cleanup in bpf_bprintf_cleanup only when needed Jiri Olsa
2022-12-17 0:25 ` Yonghong Song
2022-12-15 21:44 ` [PATCHv3 bpf-next 3/3] bpf: Remove trace_printk_lock Jiri Olsa
2022-12-17 0:28 ` Yonghong Song
2022-12-19 21:10 ` patchwork-bot+netdevbpf [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=167148421882.25912.2818674096499754269.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=revest@chromium.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--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