From: patchwork-bot+netdevbpf@kernel.org
To: Dmitrii Banshchikov <me@ubique.spb.ru>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
rdna@fb.com
Subject: Re: [PATCH v2] bpf: Drop imprecise log message
Date: Wed, 24 Feb 2021 15:50:07 +0000 [thread overview]
Message-ID: <161418180726.1820.13683950814687200129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210223090416.333943-1-me@ubique.spb.ru>
Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Tue, 23 Feb 2021 13:04:16 +0400 you wrote:
> Now it is possible for global function to have a pointer argument that
> points to something different than struct. Drop the irrelevant log
> message and keep the logic same.
>
> Fixes: e5069b9c23b3 ("bpf: Support pointers in global func args")
> Signed-off-by: Dmitrii Banshchikov <me@ubique.spb.ru>
> Acked-by: Martin KaFai Lau <kafai@fb.com>
>
> [...]
Here is the summary with links:
- [v2] bpf: Drop imprecise log message
https://git.kernel.org/bpf/bpf/c/f4eda8b6e4a5
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-02-24 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 19:57 [PATCH bpf-next] bpf: Drop imprecise log message Dmitrii Banshchikov
2021-02-22 9:10 ` [PATCH v1 " Dmitrii Banshchikov
2021-02-22 19:31 ` Martin KaFai Lau
2021-02-22 19:53 ` Dmitrii Banshchikov
2021-02-22 20:02 ` Dmitrii Banshchikov
2021-02-23 9:04 ` [PATCH v2] " Dmitrii Banshchikov
2021-02-24 15: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=161418180726.1820.13683950814687200129.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=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=me@ubique.spb.ru \
--cc=rdna@fb.com \
--cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).