* [PATCH v1 1/7] doc: fix blank lines in modify field action description
[not found] <20230516063747.3047758-1-michaelba@nvidia.com>
@ 2023-05-16 6:37 ` Michael Baum
2023-05-16 6:37 ` [PATCH v1 2/7] doc: fix blank line in asynchronous operations description Michael Baum
` (2 subsequent siblings)
3 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-16 6:37 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The modify field action description inside "Generic flow API (rte_flow)"
documentation, lists all operations supported for a destination field.
In addition, it lists the values supported for a encapsulation level
field.
Before the lists, in both cases, miss a blank line causing them to look
regular text lines.
This patch adds the blank lines.
Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 32fc45516a..e7faa368a1 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2917,20 +2917,23 @@ The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it
``RTE_FLOW_FIELD_START`` is used to point to the beginning of a packet.
See ``enum rte_flow_field_id`` for the list of supported fields.
-``op`` selects the operation to perform on a destination field.
+``op`` selects the operation to perform on a destination field:
+
- ``set`` copies the data from ``src`` field to ``dst`` field.
- ``add`` adds together ``dst`` and ``src`` and stores the result into ``dst``.
-- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``
+- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``.
``width`` defines a number of bits to use from ``src`` field.
``level`` is used to access any packet field on any encapsulation level
-as well as any tag element in the tag array.
-- ``0`` means the default behaviour. Depending on the packet type, it can
-mean outermost, innermost or anything in between.
+as well as any tag element in the tag array:
+
+- ``0`` means the default behaviour. Depending on the packet type,
+ it can mean outermost, innermost or anything in between.
- ``1`` requests access to the outermost packet encapsulation level.
- ``2`` and subsequent values requests access to the specified packet
-encapsulation level, from outermost to innermost (lower to higher values).
+ encapsulation level, from outermost to innermost (lower to higher values).
+
For the tag array (in case of multiple tags are supported and present)
``level`` translates directly into the array index.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v1 2/7] doc: fix blank line in asynchronous operations description
[not found] <20230516063747.3047758-1-michaelba@nvidia.com>
2023-05-16 6:37 ` [PATCH v1 1/7] doc: fix blank lines in modify field action description Michael Baum
@ 2023-05-16 6:37 ` Michael Baum
2023-05-17 17:13 ` Ori Kam
2023-05-16 6:37 ` [PATCH v1 3/7] doc: fix wrong indentation in RSS action description Michael Baum
[not found] ` <20230518174015.3373185-1-michaelba@nvidia.com>
3 siblings, 1 reply; 20+ messages in thread
From: Michael Baum @ 2023-05-16 6:37 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The asynchronous operations description inside "Generic flow API
(rte_flow)" documentation, adds some bullets to describe asynchronous
operations behavior.
Before the first bullet, miss a blank line causing it to look a regular
text line.
This patch adds the blank line.
Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules operations")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index e7faa368a1..76e69190fc 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -3702,6 +3702,7 @@ Asynchronous operations
-----------------------
Flow rules management can be done via special lockless flow management queues.
+
- Queue operations are asynchronous and not thread-safe.
- Operations can thus be invoked by the app's datapath,
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v1 3/7] doc: fix wrong indentation in RSS action description
[not found] <20230516063747.3047758-1-michaelba@nvidia.com>
2023-05-16 6:37 ` [PATCH v1 1/7] doc: fix blank lines in modify field action description Michael Baum
2023-05-16 6:37 ` [PATCH v1 2/7] doc: fix blank line in asynchronous operations description Michael Baum
@ 2023-05-16 6:37 ` Michael Baum
2023-05-18 6:18 ` Ori Kam
[not found] ` <20230518174015.3373185-1-michaelba@nvidia.com>
3 siblings, 1 reply; 20+ messages in thread
From: Michael Baum @ 2023-05-16 6:37 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
adrien.mazarguil, stable
The RSS action description inside "Generic flow API (rte_flow)"
documentation, lists the values supported for a encapsulation level
field.
For "2" value, it uses 3 spaces as an indentation instead of 2 after
line breaking, causing the first line to be bold.
This patch updates the number of spaces in the indentation.
Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action")
Cc: adrien.mazarguil@6wind.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 76e69190fc..25b57bf86d 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -1954,8 +1954,8 @@ Also, regarding packet encapsulation ``level``:
level.
- ``2`` and subsequent values request RSS to be performed on the specified
- inner packet encapsulation level, from outermost to innermost (lower to
- higher values).
+ inner packet encapsulation level, from outermost to innermost (lower to
+ higher values).
Values other than ``0`` are not necessarily supported.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: [PATCH v1 2/7] doc: fix blank line in asynchronous operations description
2023-05-16 6:37 ` [PATCH v1 2/7] doc: fix blank line in asynchronous operations description Michael Baum
@ 2023-05-17 17:13 ` Ori Kam
0 siblings, 0 replies; 20+ messages in thread
From: Ori Kam @ 2023-05-17 17:13 UTC (permalink / raw)
To: Michael Baum, dev
Cc: Aman Singh, Yuying Zhang, Ferruh Yigit,
NBU-Contact-Thomas Monjalon (EXTERNAL),
Alexander Kozyrev, stable
Hi Michael,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Tuesday, May 16, 2023 9:38 AM
>
> The asynchronous operations description inside "Generic flow API
> (rte_flow)" documentation, adds some bullets to describe asynchronous
> operations behavior.
>
> Before the first bullet, miss a blank line causing it to look a regular
> text line.
>
> This patch adds the blank line.
>
> Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules
> operations")
> Cc: akozyrev@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> ---
> doc/guides/prog_guide/rte_flow.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/doc/guides/prog_guide/rte_flow.rst
> b/doc/guides/prog_guide/rte_flow.rst
> index e7faa368a1..76e69190fc 100644
> --- a/doc/guides/prog_guide/rte_flow.rst
> +++ b/doc/guides/prog_guide/rte_flow.rst
> @@ -3702,6 +3702,7 @@ Asynchronous operations
> -----------------------
>
> Flow rules management can be done via special lockless flow management
> queues.
> +
> - Queue operations are asynchronous and not thread-safe.
>
> - Operations can thus be invoked by the app's datapath,
> --
> 2.25.1
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: [PATCH v1 3/7] doc: fix wrong indentation in RSS action description
2023-05-16 6:37 ` [PATCH v1 3/7] doc: fix wrong indentation in RSS action description Michael Baum
@ 2023-05-18 6:18 ` Ori Kam
0 siblings, 0 replies; 20+ messages in thread
From: Ori Kam @ 2023-05-18 6:18 UTC (permalink / raw)
To: Michael Baum, dev
Cc: Aman Singh, Yuying Zhang, Ferruh Yigit,
NBU-Contact-Thomas Monjalon (EXTERNAL),
NBU-Contact-Adrien Mazarguil (EXTERNAL),
stable
Hi Michael,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Tuesday, May 16, 2023 9:38 AM
>
> The RSS action description inside "Generic flow API (rte_flow)"
> documentation, lists the values supported for a encapsulation level
> field.
>
> For "2" value, it uses 3 spaces as an indentation instead of 2 after
> line breaking, causing the first line to be bold.
>
> This patch updates the number of spaces in the indentation.
>
> Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action")
> Cc: adrien.mazarguil@6wind.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> ---
> doc/guides/prog_guide/rte_flow.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/prog_guide/rte_flow.rst
> b/doc/guides/prog_guide/rte_flow.rst
> index 76e69190fc..25b57bf86d 100644
> --- a/doc/guides/prog_guide/rte_flow.rst
> +++ b/doc/guides/prog_guide/rte_flow.rst
> @@ -1954,8 +1954,8 @@ Also, regarding packet encapsulation ``level``:
> level.
>
> - ``2`` and subsequent values request RSS to be performed on the specified
> - inner packet encapsulation level, from outermost to innermost (lower to
> - higher values).
> + inner packet encapsulation level, from outermost to innermost (lower to
> + higher values).
>
> Values other than ``0`` are not necessarily supported.
>
> --
> 2.25.1
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v2 1/5] doc: fix blank lines in modify field action description
[not found] ` <20230518174015.3373185-1-michaelba@nvidia.com>
@ 2023-05-18 17:40 ` Michael Baum
2023-05-21 10:07 ` Ori Kam
2023-05-18 17:40 ` [PATCH v2 2/5] doc: fix blank line in asynchronous operations description Michael Baum
` (2 subsequent siblings)
3 siblings, 1 reply; 20+ messages in thread
From: Michael Baum @ 2023-05-18 17:40 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The modify field action description inside "Generic flow API (rte_flow)"
documentation, lists all operations supported for a destination field.
In addition, it lists the values supported for a encapsulation level
field.
Before the lists, in both cases, miss a blank line causing them to look
regular text lines.
This patch adds the blank lines.
Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 32fc45516a..e7faa368a1 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2917,20 +2917,23 @@ The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it
``RTE_FLOW_FIELD_START`` is used to point to the beginning of a packet.
See ``enum rte_flow_field_id`` for the list of supported fields.
-``op`` selects the operation to perform on a destination field.
+``op`` selects the operation to perform on a destination field:
+
- ``set`` copies the data from ``src`` field to ``dst`` field.
- ``add`` adds together ``dst`` and ``src`` and stores the result into ``dst``.
-- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``
+- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``.
``width`` defines a number of bits to use from ``src`` field.
``level`` is used to access any packet field on any encapsulation level
-as well as any tag element in the tag array.
-- ``0`` means the default behaviour. Depending on the packet type, it can
-mean outermost, innermost or anything in between.
+as well as any tag element in the tag array:
+
+- ``0`` means the default behaviour. Depending on the packet type,
+ it can mean outermost, innermost or anything in between.
- ``1`` requests access to the outermost packet encapsulation level.
- ``2`` and subsequent values requests access to the specified packet
-encapsulation level, from outermost to innermost (lower to higher values).
+ encapsulation level, from outermost to innermost (lower to higher values).
+
For the tag array (in case of multiple tags are supported and present)
``level`` translates directly into the array index.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v2 2/5] doc: fix blank line in asynchronous operations description
[not found] ` <20230518174015.3373185-1-michaelba@nvidia.com>
2023-05-18 17:40 ` [PATCH v2 1/5] doc: fix blank lines in modify field " Michael Baum
@ 2023-05-18 17:40 ` Michael Baum
2023-05-21 10:07 ` Ori Kam
2023-05-18 17:40 ` [PATCH v2 3/5] doc: fix wrong indentation in RSS action description Michael Baum
[not found] ` <20230522192804.3759072-1-michaelba@nvidia.com>
3 siblings, 1 reply; 20+ messages in thread
From: Michael Baum @ 2023-05-18 17:40 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The asynchronous operations description inside "Generic flow API
(rte_flow)" documentation, adds some bullets to describe asynchronous
operations behavior.
Before the first bullet, miss a blank line causing it to look a regular
text line.
This patch adds the blank line.
Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules operations")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index e7faa368a1..76e69190fc 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -3702,6 +3702,7 @@ Asynchronous operations
-----------------------
Flow rules management can be done via special lockless flow management queues.
+
- Queue operations are asynchronous and not thread-safe.
- Operations can thus be invoked by the app's datapath,
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v2 3/5] doc: fix wrong indentation in RSS action description
[not found] ` <20230518174015.3373185-1-michaelba@nvidia.com>
2023-05-18 17:40 ` [PATCH v2 1/5] doc: fix blank lines in modify field " Michael Baum
2023-05-18 17:40 ` [PATCH v2 2/5] doc: fix blank line in asynchronous operations description Michael Baum
@ 2023-05-18 17:40 ` Michael Baum
2023-05-21 10:08 ` Ori Kam
[not found] ` <20230522192804.3759072-1-michaelba@nvidia.com>
3 siblings, 1 reply; 20+ messages in thread
From: Michael Baum @ 2023-05-18 17:40 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
adrien.mazarguil, stable
The RSS action description inside "Generic flow API (rte_flow)"
documentation, lists the values supported for a encapsulation level
field.
For "2" value, it uses 3 spaces as an indentation instead of 2 after
line breaking, causing the first line to be bold.
This patch updates the number of spaces in the indentation.
Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action")
Cc: adrien.mazarguil@6wind.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 76e69190fc..25b57bf86d 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -1954,8 +1954,8 @@ Also, regarding packet encapsulation ``level``:
level.
- ``2`` and subsequent values request RSS to be performed on the specified
- inner packet encapsulation level, from outermost to innermost (lower to
- higher values).
+ inner packet encapsulation level, from outermost to innermost (lower to
+ higher values).
Values other than ``0`` are not necessarily supported.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: [PATCH v2 2/5] doc: fix blank line in asynchronous operations description
2023-05-18 17:40 ` [PATCH v2 2/5] doc: fix blank line in asynchronous operations description Michael Baum
@ 2023-05-21 10:07 ` Ori Kam
0 siblings, 0 replies; 20+ messages in thread
From: Ori Kam @ 2023-05-21 10:07 UTC (permalink / raw)
To: Michael Baum, dev
Cc: Aman Singh, Yuying Zhang, Ferruh Yigit,
NBU-Contact-Thomas Monjalon (EXTERNAL),
Alexander Kozyrev, stable
Hi Michael,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Thursday, May 18, 2023 8:40 PM
>
> The asynchronous operations description inside "Generic flow API
> (rte_flow)" documentation, adds some bullets to describe asynchronous
> operations behavior.
>
> Before the first bullet, miss a blank line causing it to look a regular
> text line.
>
> This patch adds the blank line.
>
> Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules
> operations")
> Cc: akozyrev@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> ---
> doc/guides/prog_guide/rte_flow.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/doc/guides/prog_guide/rte_flow.rst
> b/doc/guides/prog_guide/rte_flow.rst
> index e7faa368a1..76e69190fc 100644
> --- a/doc/guides/prog_guide/rte_flow.rst
> +++ b/doc/guides/prog_guide/rte_flow.rst
> @@ -3702,6 +3702,7 @@ Asynchronous operations
> -----------------------
>
> Flow rules management can be done via special lockless flow management
> queues.
> +
> - Queue operations are asynchronous and not thread-safe.
>
> - Operations can thus be invoked by the app's datapath,
> --
> 2.25.1
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: [PATCH v2 1/5] doc: fix blank lines in modify field action description
2023-05-18 17:40 ` [PATCH v2 1/5] doc: fix blank lines in modify field " Michael Baum
@ 2023-05-21 10:07 ` Ori Kam
0 siblings, 0 replies; 20+ messages in thread
From: Ori Kam @ 2023-05-21 10:07 UTC (permalink / raw)
To: Michael Baum, dev
Cc: Aman Singh, Yuying Zhang, Ferruh Yigit,
NBU-Contact-Thomas Monjalon (EXTERNAL),
Alexander Kozyrev, stable
Hi Michael,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Thursday, May 18, 2023 8:40 PM
>
> The modify field action description inside "Generic flow API (rte_flow)"
> documentation, lists all operations supported for a destination field.
> In addition, it lists the values supported for a encapsulation level
> field.
>
> Before the lists, in both cases, miss a blank line causing them to look
> regular text lines.
>
> This patch adds the blank lines.
>
> Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action")
> Cc: akozyrev@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> ---
> doc/guides/prog_guide/rte_flow.rst | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/doc/guides/prog_guide/rte_flow.rst
> b/doc/guides/prog_guide/rte_flow.rst
> index 32fc45516a..e7faa368a1 100644
> --- a/doc/guides/prog_guide/rte_flow.rst
> +++ b/doc/guides/prog_guide/rte_flow.rst
> @@ -2917,20 +2917,23 @@ The immediate value
> ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it
> ``RTE_FLOW_FIELD_START`` is used to point to the beginning of a packet.
> See ``enum rte_flow_field_id`` for the list of supported fields.
>
> -``op`` selects the operation to perform on a destination field.
> +``op`` selects the operation to perform on a destination field:
> +
> - ``set`` copies the data from ``src`` field to ``dst`` field.
> - ``add`` adds together ``dst`` and ``src`` and stores the result into ``dst``.
> -- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``
> +- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``.
>
> ``width`` defines a number of bits to use from ``src`` field.
>
> ``level`` is used to access any packet field on any encapsulation level
> -as well as any tag element in the tag array.
> -- ``0`` means the default behaviour. Depending on the packet type, it can
> -mean outermost, innermost or anything in between.
> +as well as any tag element in the tag array:
> +
> +- ``0`` means the default behaviour. Depending on the packet type,
> + it can mean outermost, innermost or anything in between.
> - ``1`` requests access to the outermost packet encapsulation level.
> - ``2`` and subsequent values requests access to the specified packet
> -encapsulation level, from outermost to innermost (lower to higher values).
> + encapsulation level, from outermost to innermost (lower to higher
> values).
> +
> For the tag array (in case of multiple tags are supported and present)
> ``level`` translates directly into the array index.
>
> --
> 2.25.1
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: [PATCH v2 3/5] doc: fix wrong indentation in RSS action description
2023-05-18 17:40 ` [PATCH v2 3/5] doc: fix wrong indentation in RSS action description Michael Baum
@ 2023-05-21 10:08 ` Ori Kam
0 siblings, 0 replies; 20+ messages in thread
From: Ori Kam @ 2023-05-21 10:08 UTC (permalink / raw)
To: Michael Baum, dev
Cc: Aman Singh, Yuying Zhang, Ferruh Yigit,
NBU-Contact-Thomas Monjalon (EXTERNAL),
NBU-Contact-Adrien Mazarguil (EXTERNAL),
stable
Hi Michael,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Thursday, May 18, 2023 8:40 PM
> To: dev@dpdk.org
>
> The RSS action description inside "Generic flow API (rte_flow)"
> documentation, lists the values supported for a encapsulation level
> field.
>
> For "2" value, it uses 3 spaces as an indentation instead of 2 after
> line breaking, causing the first line to be bold.
>
> This patch updates the number of spaces in the indentation.
>
> Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action")
> Cc: adrien.mazarguil@6wind.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> ---
> doc/guides/prog_guide/rte_flow.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/prog_guide/rte_flow.rst
> b/doc/guides/prog_guide/rte_flow.rst
> index 76e69190fc..25b57bf86d 100644
> --- a/doc/guides/prog_guide/rte_flow.rst
> +++ b/doc/guides/prog_guide/rte_flow.rst
> @@ -1954,8 +1954,8 @@ Also, regarding packet encapsulation ``level``:
> level.
>
> - ``2`` and subsequent values request RSS to be performed on the specified
> - inner packet encapsulation level, from outermost to innermost (lower to
> - higher values).
> + inner packet encapsulation level, from outermost to innermost (lower to
> + higher values).
>
> Values other than ``0`` are not necessarily supported.
>
> --
> 2.25.1
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v3 1/5] doc: fix blank lines in modify field action description
[not found] ` <20230522192804.3759072-1-michaelba@nvidia.com>
@ 2023-05-22 19:28 ` Michael Baum
2023-05-22 19:28 ` [PATCH v3 2/5] doc: fix blank line in asynchronous operations description Michael Baum
` (2 subsequent siblings)
3 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-22 19:28 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The modify field action description inside "Generic flow API (rte_flow)"
documentation, lists all operations supported for a destination field.
In addition, it lists the values supported for a encapsulation level
field.
Before the lists, in both cases, miss a blank line causing them to look
regular text lines.
This patch adds the blank lines.
Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 32fc45516a..e7faa368a1 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2917,20 +2917,23 @@ The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it
``RTE_FLOW_FIELD_START`` is used to point to the beginning of a packet.
See ``enum rte_flow_field_id`` for the list of supported fields.
-``op`` selects the operation to perform on a destination field.
+``op`` selects the operation to perform on a destination field:
+
- ``set`` copies the data from ``src`` field to ``dst`` field.
- ``add`` adds together ``dst`` and ``src`` and stores the result into ``dst``.
-- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``
+- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``.
``width`` defines a number of bits to use from ``src`` field.
``level`` is used to access any packet field on any encapsulation level
-as well as any tag element in the tag array.
-- ``0`` means the default behaviour. Depending on the packet type, it can
-mean outermost, innermost or anything in between.
+as well as any tag element in the tag array:
+
+- ``0`` means the default behaviour. Depending on the packet type,
+ it can mean outermost, innermost or anything in between.
- ``1`` requests access to the outermost packet encapsulation level.
- ``2`` and subsequent values requests access to the specified packet
-encapsulation level, from outermost to innermost (lower to higher values).
+ encapsulation level, from outermost to innermost (lower to higher values).
+
For the tag array (in case of multiple tags are supported and present)
``level`` translates directly into the array index.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v3 2/5] doc: fix blank line in asynchronous operations description
[not found] ` <20230522192804.3759072-1-michaelba@nvidia.com>
2023-05-22 19:28 ` [PATCH v3 1/5] doc: fix blank lines in modify field " Michael Baum
@ 2023-05-22 19:28 ` Michael Baum
2023-05-22 19:28 ` [PATCH v3 3/5] doc: fix wrong indentation in RSS action description Michael Baum
[not found] ` <20230523124805.3846360-1-michaelba@nvidia.com>
3 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-22 19:28 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The asynchronous operations description inside "Generic flow API
(rte_flow)" documentation, adds some bullets to describe asynchronous
operations behavior.
Before the first bullet, miss a blank line causing it to look a regular
text line.
This patch adds the blank line.
Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules operations")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index e7faa368a1..76e69190fc 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -3702,6 +3702,7 @@ Asynchronous operations
-----------------------
Flow rules management can be done via special lockless flow management queues.
+
- Queue operations are asynchronous and not thread-safe.
- Operations can thus be invoked by the app's datapath,
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v3 3/5] doc: fix wrong indentation in RSS action description
[not found] ` <20230522192804.3759072-1-michaelba@nvidia.com>
2023-05-22 19:28 ` [PATCH v3 1/5] doc: fix blank lines in modify field " Michael Baum
2023-05-22 19:28 ` [PATCH v3 2/5] doc: fix blank line in asynchronous operations description Michael Baum
@ 2023-05-22 19:28 ` Michael Baum
[not found] ` <20230523124805.3846360-1-michaelba@nvidia.com>
3 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-22 19:28 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
adrien.mazarguil, stable
The RSS action description inside "Generic flow API (rte_flow)"
documentation, lists the values supported for a encapsulation level
field.
For "2" value, it uses 3 spaces as an indentation instead of 2 after
line breaking, causing the first line to be bold.
This patch updates the number of spaces in the indentation.
Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action")
Cc: adrien.mazarguil@6wind.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 76e69190fc..25b57bf86d 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -1954,8 +1954,8 @@ Also, regarding packet encapsulation ``level``:
level.
- ``2`` and subsequent values request RSS to be performed on the specified
- inner packet encapsulation level, from outermost to innermost (lower to
- higher values).
+ inner packet encapsulation level, from outermost to innermost (lower to
+ higher values).
Values other than ``0`` are not necessarily supported.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v4 1/5] doc: fix blank lines in modify field action description
[not found] ` <20230523124805.3846360-1-michaelba@nvidia.com>
@ 2023-05-23 12:48 ` Michael Baum
2023-05-23 12:48 ` [PATCH v4 2/5] doc: fix blank line in asynchronous operations description Michael Baum
` (2 subsequent siblings)
3 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-23 12:48 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The modify field action description inside "Generic flow API (rte_flow)"
documentation, lists all operations supported for a destination field.
In addition, it lists the values supported for a encapsulation level
field.
Before the lists, in both cases, miss a blank line causing them to look
regular text lines.
This patch adds the blank lines.
Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 32fc45516a..e7faa368a1 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2917,20 +2917,23 @@ The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it
``RTE_FLOW_FIELD_START`` is used to point to the beginning of a packet.
See ``enum rte_flow_field_id`` for the list of supported fields.
-``op`` selects the operation to perform on a destination field.
+``op`` selects the operation to perform on a destination field:
+
- ``set`` copies the data from ``src`` field to ``dst`` field.
- ``add`` adds together ``dst`` and ``src`` and stores the result into ``dst``.
-- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``
+- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``.
``width`` defines a number of bits to use from ``src`` field.
``level`` is used to access any packet field on any encapsulation level
-as well as any tag element in the tag array.
-- ``0`` means the default behaviour. Depending on the packet type, it can
-mean outermost, innermost or anything in between.
+as well as any tag element in the tag array:
+
+- ``0`` means the default behaviour. Depending on the packet type,
+ it can mean outermost, innermost or anything in between.
- ``1`` requests access to the outermost packet encapsulation level.
- ``2`` and subsequent values requests access to the specified packet
-encapsulation level, from outermost to innermost (lower to higher values).
+ encapsulation level, from outermost to innermost (lower to higher values).
+
For the tag array (in case of multiple tags are supported and present)
``level`` translates directly into the array index.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v4 2/5] doc: fix blank line in asynchronous operations description
[not found] ` <20230523124805.3846360-1-michaelba@nvidia.com>
2023-05-23 12:48 ` [PATCH v4 1/5] doc: fix blank lines in modify field " Michael Baum
@ 2023-05-23 12:48 ` Michael Baum
2023-05-23 12:48 ` [PATCH v4 3/5] doc: fix wrong indentation in RSS action description Michael Baum
[not found] ` <20230523213157.3905696-1-michaelba@nvidia.com>
3 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-23 12:48 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The asynchronous operations description inside "Generic flow API
(rte_flow)" documentation, adds some bullets to describe asynchronous
operations behavior.
Before the first bullet, miss a blank line causing it to look a regular
text line.
This patch adds the blank line.
Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules operations")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index e7faa368a1..76e69190fc 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -3702,6 +3702,7 @@ Asynchronous operations
-----------------------
Flow rules management can be done via special lockless flow management queues.
+
- Queue operations are asynchronous and not thread-safe.
- Operations can thus be invoked by the app's datapath,
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v4 3/5] doc: fix wrong indentation in RSS action description
[not found] ` <20230523124805.3846360-1-michaelba@nvidia.com>
2023-05-23 12:48 ` [PATCH v4 1/5] doc: fix blank lines in modify field " Michael Baum
2023-05-23 12:48 ` [PATCH v4 2/5] doc: fix blank line in asynchronous operations description Michael Baum
@ 2023-05-23 12:48 ` Michael Baum
[not found] ` <20230523213157.3905696-1-michaelba@nvidia.com>
3 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-23 12:48 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
adrien.mazarguil, stable
The RSS action description inside "Generic flow API (rte_flow)"
documentation, lists the values supported for a encapsulation level
field.
For "2" value, it uses 3 spaces as an indentation instead of 2 after
line breaking, causing the first line to be bold.
This patch updates the number of spaces in the indentation.
Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action")
Cc: adrien.mazarguil@6wind.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 76e69190fc..25b57bf86d 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -1954,8 +1954,8 @@ Also, regarding packet encapsulation ``level``:
level.
- ``2`` and subsequent values request RSS to be performed on the specified
- inner packet encapsulation level, from outermost to innermost (lower to
- higher values).
+ inner packet encapsulation level, from outermost to innermost (lower to
+ higher values).
Values other than ``0`` are not necessarily supported.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v5 1/5] doc: fix blank lines in modify field action description
[not found] ` <20230523213157.3905696-1-michaelba@nvidia.com>
@ 2023-05-23 21:31 ` Michael Baum
2023-05-23 21:31 ` [PATCH v5 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-23 21:31 ` [PATCH v5 3/5] doc: fix wrong indentation in RSS action description Michael Baum
2 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-23 21:31 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The modify field action description inside "Generic flow API (rte_flow)"
documentation, lists all operations supported for a destination field.
In addition, it lists the values supported for a encapsulation level
field.
Before the lists, in both cases, miss a blank line causing them to look
regular text lines.
This patch adds the blank lines.
Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 32fc45516a..e7faa368a1 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -2917,20 +2917,23 @@ The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it
``RTE_FLOW_FIELD_START`` is used to point to the beginning of a packet.
See ``enum rte_flow_field_id`` for the list of supported fields.
-``op`` selects the operation to perform on a destination field.
+``op`` selects the operation to perform on a destination field:
+
- ``set`` copies the data from ``src`` field to ``dst`` field.
- ``add`` adds together ``dst`` and ``src`` and stores the result into ``dst``.
-- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``
+- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``.
``width`` defines a number of bits to use from ``src`` field.
``level`` is used to access any packet field on any encapsulation level
-as well as any tag element in the tag array.
-- ``0`` means the default behaviour. Depending on the packet type, it can
-mean outermost, innermost or anything in between.
+as well as any tag element in the tag array:
+
+- ``0`` means the default behaviour. Depending on the packet type,
+ it can mean outermost, innermost or anything in between.
- ``1`` requests access to the outermost packet encapsulation level.
- ``2`` and subsequent values requests access to the specified packet
-encapsulation level, from outermost to innermost (lower to higher values).
+ encapsulation level, from outermost to innermost (lower to higher values).
+
For the tag array (in case of multiple tags are supported and present)
``level`` translates directly into the array index.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v5 2/5] doc: fix blank line in asynchronous operations description
[not found] ` <20230523213157.3905696-1-michaelba@nvidia.com>
2023-05-23 21:31 ` [PATCH v5 1/5] doc: fix blank lines in modify field " Michael Baum
@ 2023-05-23 21:31 ` Michael Baum
2023-05-23 21:31 ` [PATCH v5 3/5] doc: fix wrong indentation in RSS action description Michael Baum
2 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-23 21:31 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
akozyrev, stable
The asynchronous operations description inside "Generic flow API
(rte_flow)" documentation, adds some bullets to describe asynchronous
operations behavior.
Before the first bullet, miss a blank line causing it to look a regular
text line.
This patch adds the blank line.
Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules operations")
Cc: akozyrev@nvidia.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index e7faa368a1..76e69190fc 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -3702,6 +3702,7 @@ Asynchronous operations
-----------------------
Flow rules management can be done via special lockless flow management queues.
+
- Queue operations are asynchronous and not thread-safe.
- Operations can thus be invoked by the app's datapath,
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [PATCH v5 3/5] doc: fix wrong indentation in RSS action description
[not found] ` <20230523213157.3905696-1-michaelba@nvidia.com>
2023-05-23 21:31 ` [PATCH v5 1/5] doc: fix blank lines in modify field " Michael Baum
2023-05-23 21:31 ` [PATCH v5 2/5] doc: fix blank line in asynchronous operations description Michael Baum
@ 2023-05-23 21:31 ` Michael Baum
2 siblings, 0 replies; 20+ messages in thread
From: Michael Baum @ 2023-05-23 21:31 UTC (permalink / raw)
To: dev
Cc: Ori Kam, Aman Singh, Yuying Zhang, Ferruh Yigit, Thomas Monjalon,
adrien.mazarguil, stable
The RSS action description inside "Generic flow API (rte_flow)"
documentation, lists the values supported for a encapsulation level
field.
For "2" value, it uses 3 spaces as an indentation instead of 2 after
line breaking, causing the first line to be bold.
This patch updates the number of spaces in the indentation.
Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action")
Cc: adrien.mazarguil@6wind.com
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
doc/guides/prog_guide/rte_flow.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 76e69190fc..25b57bf86d 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -1954,8 +1954,8 @@ Also, regarding packet encapsulation ``level``:
level.
- ``2`` and subsequent values request RSS to be performed on the specified
- inner packet encapsulation level, from outermost to innermost (lower to
- higher values).
+ inner packet encapsulation level, from outermost to innermost (lower to
+ higher values).
Values other than ``0`` are not necessarily supported.
--
2.25.1
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2023-05-23 21:32 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20230516063747.3047758-1-michaelba@nvidia.com>
2023-05-16 6:37 ` [PATCH v1 1/7] doc: fix blank lines in modify field action description Michael Baum
2023-05-16 6:37 ` [PATCH v1 2/7] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-17 17:13 ` Ori Kam
2023-05-16 6:37 ` [PATCH v1 3/7] doc: fix wrong indentation in RSS action description Michael Baum
2023-05-18 6:18 ` Ori Kam
[not found] ` <20230518174015.3373185-1-michaelba@nvidia.com>
2023-05-18 17:40 ` [PATCH v2 1/5] doc: fix blank lines in modify field " Michael Baum
2023-05-21 10:07 ` Ori Kam
2023-05-18 17:40 ` [PATCH v2 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-21 10:07 ` Ori Kam
2023-05-18 17:40 ` [PATCH v2 3/5] doc: fix wrong indentation in RSS action description Michael Baum
2023-05-21 10:08 ` Ori Kam
[not found] ` <20230522192804.3759072-1-michaelba@nvidia.com>
2023-05-22 19:28 ` [PATCH v3 1/5] doc: fix blank lines in modify field " Michael Baum
2023-05-22 19:28 ` [PATCH v3 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-22 19:28 ` [PATCH v3 3/5] doc: fix wrong indentation in RSS action description Michael Baum
[not found] ` <20230523124805.3846360-1-michaelba@nvidia.com>
2023-05-23 12:48 ` [PATCH v4 1/5] doc: fix blank lines in modify field " Michael Baum
2023-05-23 12:48 ` [PATCH v4 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-23 12:48 ` [PATCH v4 3/5] doc: fix wrong indentation in RSS action description Michael Baum
[not found] ` <20230523213157.3905696-1-michaelba@nvidia.com>
2023-05-23 21:31 ` [PATCH v5 1/5] doc: fix blank lines in modify field " Michael Baum
2023-05-23 21:31 ` [PATCH v5 2/5] doc: fix blank line in asynchronous operations description Michael Baum
2023-05-23 21:31 ` [PATCH v5 3/5] doc: fix wrong indentation in RSS action description Michael Baum
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).