| Message ID | 20201028044609.18581-1-ajit.khaparde@broadcom.com (mailing list archive) |
|---|---|
| State | Accepted, archived |
| Delegated to: | Andrew Rybchenko |
| Headers | show |
| Series | doc: fix a typo in rte flow guide | expand |
| Context | Check | Description |
|---|---|---|
| ci/travis-robot | success | Travis build: passed |
| ci/Intel-compilation | success | Compilation OK |
| ci/checkpatch | success | coding style OK |
On 10/28/20 7:46 AM, Ajit Khaparde wrote: > flow_type_rss_offloads was misspelt as flow_tpe_rss_offloads > > Fixes: 6abee736abe6 ("doc: update RSS flow action with best effort") > Cc: stable@dpdk.org > > Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> Applied to dpdk-next-net/main, thanks.
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index 8dc048c6f4..ea203e0ca4 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -1778,7 +1778,7 @@ these RSS types are simply ignored. For example, it happens if: (e.g. pattern has UDP item, but RSS types contain TCP). If requested RSS hash types are not supported by the Ethernet device at all -(not reported in ``dev_info.flow_tpe_rss_offloads``), +(not reported in ``dev_info.flow_type_rss_offloads``), the flow creation will fail. Note: RSS hash result is stored in the ``hash.rss`` mbuf field which
flow_type_rss_offloads was misspelt as flow_tpe_rss_offloads Fixes: 6abee736abe6 ("doc: update RSS flow action with best effort") Cc: stable@dpdk.org Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> --- doc/guides/prog_guide/rte_flow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)