From: patchwork-bot+netdevbpf@kernel.org
To: Louis DeLosSantos <louis.delos.devel@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
martin.lau@linux.dev, sdf@google.com, razor@blackwall.org,
john.fastabend@gmail.com, yhs@meta.com
Subject: Re: [PATCH v2 0/2] bpf: utilize table ID in bpf_fib_lookup helper
Date: Thu, 01 Jun 2023 18:10:19 +0000 [thread overview]
Message-ID: <168564301912.9357.10823753179270700264.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230505-bpf-add-tbid-fib-lookup-v2-0-0a31c22c748c@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 31 May 2023 15:38:47 -0400 you wrote:
> This patchset adds the ability to specify a table ID to the
> `bpf_fib_lookup` BPF helper.
>
> A new `tbid` field is added to `struct fib_bpf_lookup`.
> When the `fib_bpf_lookup` helper is called with the `BPF_FIB_LOOKUP_DIRECT` and
> `BPF_FIB_LOOKUP_TBID' flag the `tbid` field will be interpreted as the table ID
> to use for the fib lookup.
>
> [...]
Here is the summary with links:
- [v2,1/2] bpf: add table ID to bpf_fib_lookup BPF helper
https://git.kernel.org/bpf/bpf-next/c/8ad77e72caae
- [v2,2/2] selftests/bpf: test table ID fib lookup BPF helper
https://git.kernel.org/bpf/bpf-next/c/d4ae3e587ece
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:[~2023-06-01 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 19:38 [PATCH v2 0/2] bpf: utilize table ID in bpf_fib_lookup helper Louis DeLosSantos
2023-05-31 19:38 ` [PATCH v2 1/2] bpf: add table ID to bpf_fib_lookup BPF helper Louis DeLosSantos
2023-05-31 19:38 ` [PATCH v2 2/2] selftests/bpf: test table ID fib lookup " Louis DeLosSantos
2023-06-01 18:07 ` [PATCH v2 0/2] bpf: utilize table ID in bpf_fib_lookup helper Daniel Borkmann
2023-06-01 18: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=168564301912.9357.10823753179270700264.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=john.fastabend@gmail.com \
--cc=louis.delos.devel@gmail.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=sdf@google.com \
--cc=yhs@meta.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