From: patchwork-bot+netdevbpf@kernel.org
To: Dimitris Michailidis <d.michailidis@fungible.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
rdunlap@infradead.org
Subject: Re: [PATCH net-next 0/2] net/fungible: fix errors when CONFIG_TLS_DEVICE=n
Date: Thu, 10 Mar 2022 04:20:11 +0000 [thread overview]
Message-ID: <164688601129.11305.324459189637319013.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220309034032.405212-1-dmichail@fungible.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Mar 2022 19:40:30 -0800 you wrote:
> This pair of patches fix compile errors in funeth when
> CONFIG_TLS_DEVICE=n. The errors are due to symbols that are not defined
> in this config but are used in code guarded by
> "if (IS_ENABLED(CONFIG_TLS_DEVICE) ..."
>
> One option is to place this code under preprocessor guards that will
> keep the compiler from looking at the code. The option adopted here is
> to define the offending symbols also when CONFIG_TLS_DEVICE=n.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net/tls: Provide {__,}tls_driver_ctx() unconditionally
https://git.kernel.org/netdev/net-next/c/77f09e66f613
- [net-next,2/2] net/fungible: fix errors when CONFIG_TLS_DEVICE=n
https://git.kernel.org/netdev/net-next/c/b23f9239195a
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-03-10 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 3:40 [PATCH net-next 0/2] net/fungible: fix errors when CONFIG_TLS_DEVICE=n Dimitris Michailidis
2022-03-09 3:40 ` [PATCH net-next 1/2] net/tls: Provide {__,}tls_driver_ctx() unconditionally Dimitris Michailidis
2022-03-09 6:00 ` Jakub Kicinski
2022-03-09 3:40 ` [PATCH net-next 2/2] net/fungible: fix errors when CONFIG_TLS_DEVICE=n Dimitris Michailidis
2022-03-10 4:20 ` 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=164688601129.11305.324459189637319013.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=d.michailidis@fungible.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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).