public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
* [PATCH] virtio-net: Fix ipsec broken conformance links
@ 2025-07-09 14:00 Parav Pandit
  2025-07-09 16:25 ` Matias Ezequiel Vara Larsen
  0 siblings, 1 reply; 3+ messages in thread
From: Parav Pandit @ 2025-07-09 14:00 UTC (permalink / raw)
  To: virtio-comment, mst, cohuck, mvaralar; +Cc: shahafs, Parav Pandit

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


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] virtio-net: Fix ipsec broken conformance links
  2025-07-09 14:00 [PATCH] virtio-net: Fix ipsec broken conformance links Parav Pandit
@ 2025-07-09 16:25 ` Matias Ezequiel Vara Larsen
  2025-07-15  7:02   ` Parav Pandit
  0 siblings, 1 reply; 3+ messages in thread
From: Matias Ezequiel Vara Larsen @ 2025-07-09 16:25 UTC (permalink / raw)
  To: Parav Pandit; +Cc: virtio-comment, mst, cohuck, shahafs

On Wed, Jul 09, 2025 at 05:00:49PM +0300, Parav Pandit wrote:
> 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(-)
> 

Reviewed-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>

> 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
> 


^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [PATCH] virtio-net: Fix ipsec broken conformance links
  2025-07-09 16:25 ` Matias Ezequiel Vara Larsen
@ 2025-07-15  7:02   ` Parav Pandit
  0 siblings, 0 replies; 3+ messages in thread
From: Parav Pandit @ 2025-07-15  7:02 UTC (permalink / raw)
  To: Matias Ezequiel Vara Larsen
  Cc: virtio-comment@lists.linux.dev, mst@redhat.com, cohuck@redhat.com,
	Shahaf Shuler


> From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> Sent: 09 July 2025 09:55 PM
> To: Parav Pandit <parav@nvidia.com>
> Cc: virtio-comment@lists.linux.dev; mst@redhat.com; cohuck@redhat.com;
> Shahaf Shuler <shahafs@nvidia.com>
> Subject: Re: [PATCH] virtio-net: Fix ipsec broken conformance links
> 
> On Wed, Jul 09, 2025 at 05:00:49PM +0300, Parav Pandit wrote:
> > 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(-)
> >
> 
> Reviewed-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> 
This editorial change of 'Net' to 'Network' correction is merged.
Thanks.

> > 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
> >


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-07-15  7:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-09 14:00 [PATCH] virtio-net: Fix ipsec broken conformance links Parav Pandit
2025-07-09 16:25 ` Matias Ezequiel Vara Larsen
2025-07-15  7:02   ` Parav Pandit

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox