From: patchwork-bot+netdevbpf@kernel.org
To: Rafael Passos <rafael@rcpassos.me>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH] bpf: fix typo in function save_aux_ptr_type
Date: Mon, 22 Apr 2024 15:20:27 +0000 [thread overview]
Message-ID: <171379922702.23349.7247861491314887893.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fbe1d636-8172-4698-9a5a-5a3444b55322@smtp-relay.sendinblue.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 17 Apr 2024 14:52:26 -0300 you wrote:
> I found this typo in the save_aux_ptr_type function.
> s/allow_trust_missmatch/allow_trust_mismatch/
> I did not find this anywhere else in the codebase.
>
> Signed-off-by: Rafael Passos <rafael@rcpassos.me>
> ---
> kernel/bpf/verifier.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Here is the summary with links:
- bpf: fix typo in function save_aux_ptr_type
https://git.kernel.org/bpf/bpf-next/c/e1a7545981e2
- [bpf-next,2/2] bpf: fix typo in function save_aux_ptr_type
https://git.kernel.org/bpf/bpf-next/c/e1a7545981e2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-04-22 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240417180446.9300-1-rafael@rcpassos.me>
2024-04-17 17:52 ` [PATCH] bpf: fix typo in function save_aux_ptr_type Rafael Passos
2024-04-22 15:20 ` patchwork-bot+netdevbpf [this message]
2024-04-17 18:49 ` [PATCH bpf-next 1/2] bpf: fixes typos in comments Rafael Passos
2024-04-22 16:00 ` patchwork-bot+netdevbpf
[not found] ` <20240417184918.21472-1-rafael@rcpassos.me>
2024-04-17 18:49 ` [PATCH bpf-next 2/2] bpf: fix typo in function save_aux_ptr_type Rafael Passos
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=171379922702.23349.7247861491314887893.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=rafael@rcpassos.me \
/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