From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
tsbogend@alpha.franken.de, johan.almbladh@anyfinetworks.com,
paulburton@kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, lixuefeng@loongson.cn,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] bpf, mips: Do some small changes
Date: Mon, 11 Oct 2021 13:40:06 +0000 [thread overview]
Message-ID: <163395960692.3494.2058779549253903670.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1633915150-13220-1-git-send-email-yangtiezhu@loongson.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 11 Oct 2021 09:19:08 +0800 you wrote:
> This patchset is based on bpf-next tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
>
> v2:
> -- Update patch #2 to only fix the comment,
> suggested by Johan Almbladh, thank you.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf, mips: Clean up config options about JIT
https://git.kernel.org/bpf/bpf-next/c/307d149d9435
- [bpf-next,v2,2/2] bpf, mips: Fix comment on tail call count limiting
https://git.kernel.org/bpf/bpf-next/c/431bfb9ee3e2
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-10-11 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 1:19 [PATCH bpf-next v2 0/2] bpf, mips: Do some small changes Tiezhu Yang
2021-10-11 1:19 ` [PATCH bpf-next v2 1/2] bpf, mips: Clean up config options about JIT Tiezhu Yang
2021-10-11 1:19 ` [PATCH bpf-next v2 2/2] bpf, mips: Fix comment on tail call count limiting Tiezhu Yang
2021-10-11 8:13 ` Johan Almbladh
2021-10-11 13:40 ` 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=163395960692.3494.2058779549253903670.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=johan.almbladh@anyfinetworks.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=netdev@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=songliubraving@fb.com \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
--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).