From: patchwork-bot+netdevbpf@kernel.org
To: Rong Tao <rtoax@foxmail.com>
Cc: sdf@google.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
rongtao@cestc.cn, song@kernel.org, yhs@fb.com
Subject: Re: [PATCH bpf-next] samples/bpf: Replace blk_account_io_done() with __blk_account_io_done()
Date: Wed, 21 Sep 2022 00:30:14 +0000 [thread overview]
Message-ID: <166372021474.352.13363570014654346928.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_1CC476835C219FACD84B6715F0D785517E07@qq.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sun, 11 Sep 2022 21:03:30 +0800 you wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> Since commit be6bfe36db17 ("block: inline hot paths of blk_account_io_*()")
> blk_account_io_*() become inline functions.
>
> Signed-off-by: Rong Tao <rtoax@foxmail.com>
>
> [...]
Here is the summary with links:
- [bpf-next] samples/bpf: Replace blk_account_io_done() with __blk_account_io_done()
https://git.kernel.org/bpf/bpf-next/c/bc069da65eec
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-09-21 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 8:04 [PATCH bpf RESEND] samples/bpf: Replace blk_account_io_done() with __blk_account_io_done() Rong Tao
2022-09-09 16:48 ` sdf
2022-09-11 13:03 ` [PATCH bpf-next] " Rong Tao
2022-09-20 0:12 ` Yonghong Song
2022-09-21 0:30 ` 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=166372021474.352.13363570014654346928.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=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.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 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.