From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadfed@meta.com>
Cc: vadim.fedorenko@linux.dev, kuba@kernel.org, martin.lau@linux.dev,
andrii@kernel.org, ast@kernel.org, mykolal@fb.com,
herbert@gondor.apana.org.au, netdev@vger.kernel.org,
linux-crypto@vger.kernel.org, bpf@vger.kernel.org, lkp@intel.com
Subject: Re: [PATCH bpf-next] bpf: crypto: fix build when CONFIG_CRYPTO=m
Date: Wed, 01 May 2024 20:40:31 +0000 [thread overview]
Message-ID: <171459603198.27515.15117026972576302125.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240501170130.1682309-1-vadfed@meta.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 1 May 2024 10:01:30 -0700 you wrote:
> Crypto subsytem can be build as a module. In this case we still have to
> build BPF crypto framework otherwise the build will fail.
>
> Fixes: 3e1c6f35409f ("bpf: make common crypto API for TC/XDP programs")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202405011634.4JK40epY-lkp@intel.com/
> Signed-off-by: Vadim Fedorenko <vadfed@meta.com>
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: crypto: fix build when CONFIG_CRYPTO=m
https://git.kernel.org/bpf/bpf-next/c/ac2f438c2a85
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:[~2024-05-01 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 17:01 [PATCH bpf-next] bpf: crypto: fix build when CONFIG_CRYPTO=m Vadim Fedorenko
2024-05-01 20: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=171459603198.27515.15117026972576302125.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=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=vadfed@meta.com \
--cc=vadim.fedorenko@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).