From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.linux.dev>, <mst@redhat.com>,
<cohuck@redhat.com>, <mvaralar@redhat.com>
Cc: <shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH] virtio-net: Fix ipsec broken conformance links
Date: Wed, 9 Jul 2025 17:00:49 +0300 [thread overview]
Message-ID: <20250709140049.507870-1-parav@nvidia.com> (raw)
Fix the broken conformance links for ipsec device and driver
requirements.
Fixes: a0b809a7ddbd ("virtio-net: Add IPsec operation device and driver requirements")
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
device-types/net/description.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/device-types/net/description.tex b/device-types/net/description.tex
index 415c7fd..da9ff17 100644
--- a/device-types/net/description.tex
+++ b/device-types/net/description.tex
@@ -3599,7 +3599,7 @@ \subsubsection{IPsec Operation}\label{sec:Device Types / Network Device / Device
See \hyperref[par:Device Types / Crypto Device / Device Operation / IPsec Service Operation / Resource objects / VIRTIO-CRYPTO-RESOURCE-OBJ-IPSEC-INBOUND-SA]{VIRTIO_NET_RESOURCE_OBJ_IPSEC_INB_SA}.
-\devicenormative{\paragraph}{IPsec Operation}{Device Types / Net Device / Device Operation / IPsec Operation}
+\devicenormative{\paragraph}{IPsec Operation}{Device Types / Network Device / Device Operation / IPsec Operation}
When the device supports IPsec operations,
\begin{itemize}
@@ -3656,7 +3656,7 @@ \subsubsection{IPsec Operation}\label{sec:Device Types / Network Device / Device
On device reset, the device MUST destroy all the resource objects which have been created.
-\drivernormative{\paragraph}{IPsec Operation}{Device Types / Net Device / Device Operation / IPsec Operation}
+\drivernormative{\paragraph}{IPsec Operation}{Device Types / Network Device / Device Operation / IPsec Operation}
The driver MUST query the capabilities using VIRTIO_ADMIN_CMD_CAP_ID_LIST_QUERY
to discover the capability types the device offers.
--
2.34.1
next reply other threads:[~2025-07-09 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 14:00 Parav Pandit [this message]
2025-07-09 16:25 ` [PATCH] virtio-net: Fix ipsec broken conformance links Matias Ezequiel Vara Larsen
2025-07-15 7:02 ` Parav Pandit
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=20250709140049.507870-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.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