From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
kafai@fb.com, songliubraving@fb.com, haoluo@google.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
jolsa@kernel.org, mhiramat@kernel.org, akpm@linux-foundation.org,
void@manifault.com, swboyd@chromium.org, ndesaulniers@google.com,
9erthalion6@gmail.com, kennyyu@fb.com, geliang.tang@suse.com,
kuniyu@amazon.co.jp, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 bpf-next 0/2] bpf: add a ksym BPF iterator
Date: Tue, 12 Jul 2022 22:40:13 +0000 [thread overview]
Message-ID: <165766561331.1577.12047199920533136622.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1657629105-7812-1-git-send-email-alan.maguire@oracle.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 12 Jul 2022 13:31:43 +0100 you wrote:
> a ksym BPF iterator would be useful as it would allow more flexible
> interactions with kernel symbols than are currently supported; it could
> for example create more efficient map representations for lookup,
> speed up symbol resolution etc.
>
> The idea was initially discussed here [1].
>
> [...]
Here is the summary with links:
- [v6,bpf-next,1/2] bpf: add a ksym BPF iterator
https://git.kernel.org/bpf/bpf-next/c/647cafa22349
- [v6,bpf-next,2/2] selftests/bpf: add a ksym iter subtest
https://git.kernel.org/bpf/bpf-next/c/a9d2fae89fa8
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-07-12 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 12:31 [PATCH v6 bpf-next 0/2] bpf: add a ksym BPF iterator Alan Maguire
2022-07-12 12:31 ` [PATCH v6 bpf-next 1/2] " Alan Maguire
2022-07-12 12:31 ` [PATCH v6 bpf-next 2/2] selftests/bpf: add a ksym iter subtest Alan Maguire
2022-07-12 22:40 ` 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=165766561331.1577.12047199920533136622.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=9erthalion6@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=geliang.tang@suse.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kennyyu@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuniyu@amazon.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=ndesaulniers@google.com \
--cc=songliubraving@fb.com \
--cc=swboyd@chromium.org \
--cc=void@manifault.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