From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org,
maciej.fijalkowski@intel.com, kernel-team@cloudflare.com
Subject: Re: [PATCH bpf-next v2 0/2] Fix tail call counting with bpf2bpf
Date: Thu, 16 Jun 2022 19:50:13 +0000 [thread overview]
Message-ID: <165540901378.6261.15158160750256400048.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220616162037.535469-1-jakub@cloudflare.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 16 Jun 2022 18:20:35 +0200 you wrote:
> Please see patch 1 for the explanation of the problem.
> Patch 2 adds a test so that we don't regress.
>
> v1 -> v2:
> - switch from __attibute__((always_unused)) to unused to avoid CI failures.
>
> Jakub Sitnicki (2):
> bpf, x86: Fix tail call count offset calculation on bpf2bpf call
> selftests/bpf: Test tail call counting with bpf2bpf and data on stack
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf, x86: Fix tail call count offset calculation on bpf2bpf call
https://git.kernel.org/bpf/bpf/c/ff672c67ee76
- [bpf-next,v2,2/2] selftests/bpf: Test tail call counting with bpf2bpf and data on stack
https://git.kernel.org/bpf/bpf/c/5e0b0a4c52d3
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-06-16 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 16:20 [PATCH bpf-next v2 0/2] Fix tail call counting with bpf2bpf Jakub Sitnicki
2022-06-16 16:20 ` [PATCH bpf-next v2 1/2] bpf, x86: Fix tail call count offset calculation on bpf2bpf call Jakub Sitnicki
2022-06-16 16:20 ` [PATCH bpf-next v2 2/2] selftests/bpf: Test tail call counting with bpf2bpf and data on stack Jakub Sitnicki
2022-06-16 19:50 ` 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=165540901378.6261.15158160750256400048.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=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.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).