From: patchwork-bot+netdevbpf@kernel.org
To: Xu Kuohai <xukuohai@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, ivan@cloudflare.com,
ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
bjorn@kernel.org, pulehui@huawei.com
Subject: Re: [PATCH bpf-next 0/2] Fix incorrect bpf runtime stats for arm64 and riscv64
Date: Tue, 16 Apr 2024 15:30:28 +0000 [thread overview]
Message-ID: <171328142826.29407.1876399986836922707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240416064208.2919073-1-xukuohai@huaweicloud.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 16 Apr 2024 14:42:06 +0800 you wrote:
> From: Xu Kuohai <xukuohai@huawei.com>
>
> Fix incorrect bpf runtime stats for arm64 and riscv64.
>
> Xu Kuohai (2):
> bpf, arm64: Fix incorrect runtime stats
> riscv, bpf: Fix incorrect runtime stats
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf, arm64: Fix incorrect runtime stats
https://git.kernel.org/bpf/bpf/c/dc7d7447b56b
- [bpf-next,2/2] riscv, bpf: Fix incorrect runtime stats
https://git.kernel.org/bpf/bpf/c/10541b374aa0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-04-16 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 6:42 [PATCH bpf-next 0/2] Fix incorrect bpf runtime stats for arm64 and riscv64 Xu Kuohai
2024-04-16 6:42 ` [PATCH bpf-next 1/2] bpf, arm64: Fix incorrect runtime stats Xu Kuohai
2024-04-16 6:42 ` [PATCH bpf-next 2/2] riscv, bpf: " Xu Kuohai
2024-04-16 9:35 ` Pu Lehui
2024-04-16 14:09 ` Björn Töpel
2024-04-16 15: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=171328142826.29407.1876399986836922707.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ivan@cloudflare.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=pulehui@huawei.com \
--cc=xukuohai@huaweicloud.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