From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH ipsec] xfrm: Export symbol xfrm_dev_state_delete.
Date: Sun, 30 Jun 2024 13:43:11 +0300 [thread overview]
Message-ID: <20240630104311.GA176465@unreal> (raw)
In-Reply-To: <Zn54YVkoA+OOoz+C@gauss3.secunet.de>
On Fri, Jun 28, 2024 at 10:46:25AM +0200, Steffen Klassert wrote:
> This fixes a build failure if xfrm_user is build as a module.
>
> Fixes: 07b87f9eea0c ("xfrm: Fix unregister netdevice hang on hardware offload.")
> Reported-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
> ---
> net/xfrm/xfrm_state.c | 1 +
> 1 file changed, 1 insertion(+)
>
Thanks,
Tested-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2024-06-30 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 8:46 [PATCH ipsec] xfrm: Export symbol xfrm_dev_state_delete Steffen Klassert
2024-06-30 10:43 ` Leon Romanovsky [this message]
2024-07-01 21:21 ` Steffen Klassert
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=20240630104311.GA176465@unreal \
--to=leon@kernel.org \
--cc=broonie@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).