From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
lixuefeng@loongson.cn, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] Modify some code in sysctl_net_core.c
Date: Tue, 10 May 2022 17:30:12 +0000 [thread overview]
Message-ID: <165220381256.21854.15122506494053007856.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1652153703-22729-1-git-send-email-yangtiezhu@loongson.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 10 May 2022 11:35:01 +0800 you wrote:
> Tiezhu Yang (2):
> net: sysctl: Use SYSCTL_TWO instead of &two
> bpf: Print some info if disable bpf_jit_enable failed
>
> net/core/sysctl_net_core.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
Here is the summary with links:
- [bpf-next,v2,1/2] net: sysctl: Use SYSCTL_TWO instead of &two
https://git.kernel.org/bpf/bpf-next/c/f922c8972fb5
- [bpf-next,v2,2/2] bpf: Print some info if disable bpf_jit_enable failed
https://git.kernel.org/bpf/bpf-next/c/174efa781165
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-05-10 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 3:35 [PATCH bpf-next v2 0/2] Modify some code in sysctl_net_core.c Tiezhu Yang
2022-05-10 3:35 ` [PATCH bpf-next v2 1/2] net: sysctl: Use SYSCTL_TWO instead of &two Tiezhu Yang
2022-05-10 3:35 ` [PATCH bpf-next v2 2/2] bpf: Print some info if disable bpf_jit_enable failed Tiezhu Yang
2022-05-10 17: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=165220381256.21854.15122506494053007856.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=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yangtiezhu@loongson.cn \
/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).