From: patchwork-bot+netdevbpf@kernel.org
To: Larysa Zaremba <larysa.zaremba@intel.com>
Cc: quentin@isovalent.com, sdf@google.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
song@kernel.org, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
niklas.soderlund@corigine.com
Subject: Re: [PATCH bpf-next v2] bpftool: specify XDP Hints ifname when loading program
Date: Tue, 23 May 2023 15:00:20 +0000 [thread overview]
Message-ID: <168485402041.5478.8959103942618026686.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230517160103.1088185-1-larysa.zaremba@intel.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 17 May 2023 18:01:04 +0200 you wrote:
> Add ability to specify a network interface used to resolve
> XDP Hints kfuncs when loading program through bpftool.
>
> Usage:
> bpftool prog load [...] xdpmeta_dev <ifname>
>
> Writing just 'dev <ifname>' instead of 'xdpmeta_dev' is a very probable
> mistake that results in not very descriptive errors,
> so 'bpftool prog load [...] dev <ifname>' syntax becomes deprecated,
> followed by 'bpftool map create [...] dev <ifname>' for consistency.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpftool: specify XDP Hints ifname when loading program
https://git.kernel.org/bpf/bpf-next/c/f46392ee3dec
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-05-23 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 16:01 [PATCH bpf-next v2] bpftool: specify XDP Hints ifname when loading program Larysa Zaremba
2023-05-22 10:11 ` Larysa Zaremba
2023-05-22 13:24 ` Quentin Monnet
2023-05-23 15:00 ` 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=168485402041.5478.8959103942618026686.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=kpsingh@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=niklas.soderlund@corigine.com \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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