From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: ast@kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, llvm@lists.linux.dev,
linux-kernel@vger.kernel.org, ,
""@meta.com
Subject: Re: [PATCH bpf-next 0/2] Fixes for kfunc prototype generation
Date: Thu, 13 Jun 2024 18:20:30 +0000 [thread overview]
Message-ID: <171830283072.12313.15051014857766473661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1718295425.git.dxu@dxuuu.xyz>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 13 Jun 2024 10:19:24 -0600 you wrote:
> This patchset fixes new warnings and errors that kfunc prototype
> generation caused.
>
> Daniel Xu (2):
> bpf: Fix bpf_dynptr documentation comments
> bpf: selftests: Do not use generated kfunc prototypes for arena progs
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Fix bpf_dynptr documentation comments
https://git.kernel.org/bpf/bpf-next/c/78746f93e903
- [bpf-next,2/2] bpf: selftests: Do not use generated kfunc prototypes for arena progs
https://git.kernel.org/bpf/bpf-next/c/6a8260147745
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:[~2024-06-13 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 16:19 [PATCH bpf-next 0/2] Fixes for kfunc prototype generation Daniel Xu
2024-06-13 16:19 ` [PATCH bpf-next 1/2] bpf: Fix bpf_dynptr documentation comments Daniel Xu
2024-06-13 16:19 ` [PATCH bpf-next 2/2] bpf: selftests: Do not use generated kfunc prototypes for arena progs Daniel Xu
2024-06-13 18:20 ` 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=171830283072.12313.15051014857766473661.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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