From: patchwork-bot+netdevbpf@kernel.org
To: Matt Cover <werekraken@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
jakub.kicinski@netronome.com, hawk@kernel.org,
john.fastabend@gmail.com, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, kpsingh@kernel.org,
lorenzo@kernel.org, matthew.cover@stackpath.com,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] samples/bpf: xdp_redirect_cpu: Add mprog-disable to optstring.
Date: Wed, 04 Aug 2021 22:50:05 +0000 [thread overview]
Message-ID: <162811740542.13655.7097622991414354603.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210731005632.13228-1-matthew.cover@stackpath.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 30 Jul 2021 17:56:32 -0700 you wrote:
> Commit ce4dade7f12a ("samples/bpf: xdp_redirect_cpu: Load a eBPF program
> on cpumap") added the following option, but missed adding it to optstring:
> - mprog-disable: disable loading XDP program on cpumap entries
>
> Add the missing option character.
>
> Fixes: ce4dade7f12a ("samples/bpf: xdp_redirect_cpu: Load a eBPF program on cpumap")
> Signed-off-by: Matthew Cover <matthew.cover@stackpath.com>
>
> [...]
Here is the summary with links:
- [bpf-next] samples/bpf: xdp_redirect_cpu: Add mprog-disable to optstring.
https://git.kernel.org/bpf/bpf-next/c/34ad6d9d8c27
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:[~2021-08-04 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 0:56 [PATCH bpf-next] samples/bpf: xdp_redirect_cpu: Add mprog-disable to optstring Matthew Cover
2021-07-31 15:25 ` Kumar Kartikeya Dwivedi
2021-08-04 17:57 ` Matt Cover
2021-08-04 22:50 ` Daniel Borkmann
2021-08-04 22: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=162811740542.13655.7097622991414354603.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=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthew.cover@stackpath.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=werekraken@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.