From: patchwork-bot+netdevbpf@kernel.org
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: ast@kernel.org, andrii.nakryiko@gmail.com,
dan.carpenter@oracle.com, kernel-janitors@vger.kernel.org,
rostedt@goodmis.org, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] fprobe: Fixes for Sparse and Smatch warnings
Date: Tue, 29 Mar 2022 02:20:12 +0000 [thread overview]
Message-ID: <164852041242.3757.15751806635224155365.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <164802091567.1732982.1242854551611267542.stgit@devnote2>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 23 Mar 2022 16:35:15 +0900 you wrote:
> Hi,
>
> These fprobe patches are for fixing the warnings by Smatch and sparse.
> This is arch independent part of the fixes.
>
>
> Thank you,
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] fprobe: Fix smatch type mismatch warning
https://git.kernel.org/bpf/bpf/c/9052e4e83762
- [bpf-next,2/2] fprobe: Fix sparse warning for acccessing __rcu ftrace_hash
https://git.kernel.org/bpf/bpf/c/261608f3105c
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:[~2022-03-29 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 7:35 [PATCH bpf-next 0/2] fprobe: Fixes for Sparse and Smatch warnings Masami Hiramatsu
2022-03-23 7:35 ` [PATCH bpf-next 1/2] fprobe: Fix smatch type mismatch warning Masami Hiramatsu
2022-03-23 7:35 ` [PATCH bpf-next 2/2] fprobe: Fix sparse warning for acccessing __rcu ftrace_hash Masami Hiramatsu
2022-03-29 2:20 ` 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=164852041242.3757.15751806635224155365.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/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