From: patchwork-bot+netdevbpf@kernel.org
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: qmo@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, abaci@linux.alibaba.com
Subject: Re: [PATCH -next v2 1/2] bpf: Remove duplicate crypto/sha2.h header
Date: Sat, 27 Sep 2025 11:30:07 +0000 [thread overview]
Message-ID: <175897260752.228897.11178776166648300229.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250926095240.3397539-1-jiapeng.chong@linux.alibaba.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 26 Sep 2025 17:52:39 +0800 you wrote:
> ./include/linux/bpf.h: crypto/sha2.h is included more than once.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=25501
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> Changes in v2:
> -Combine two patches into a single patch series.
>
> [...]
Here is the summary with links:
- [-next,v2,1/2] bpf: Remove duplicate crypto/sha2.h header
https://git.kernel.org/bpf/bpf-next/c/87608c2a7718
- [-next,v2,2/2] bpftool: Remove duplicate string.h header
https://git.kernel.org/bpf/bpf-next/c/4b2113413e76
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:[~2025-09-27 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 9:52 [PATCH -next v2 1/2] bpf: Remove duplicate crypto/sha2.h header Jiapeng Chong
2025-09-26 9:52 ` [PATCH -next v2 2/2] bpftool: Remove duplicate string.h header Jiapeng Chong
2025-09-26 10:33 ` Quentin Monnet
2025-09-26 10:33 ` [PATCH -next v2 1/2] bpf: Remove duplicate crypto/sha2.h header Quentin Monnet
2025-09-27 11: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=175897260752.228897.11178776166648300229.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=abaci@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jiapeng.chong@linux.alibaba.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=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.