A leading '0' was missed of the hexadecimal value. Fixes: 3ceeed9f7855 ("doc: update flow mark action in mlx5 guide") Cc: viachesl...@nvidia.com Cc: sta...@dpdk.org
Signed-off-by: Bing Zhao <bi...@nvidia.com> Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com> --- doc/guides/nics/mlx5.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index feb2e57cee..176f890b0d 100644 --- a/doc/guides/nics/mlx5.rst +++ b/doc/guides/nics/mlx5.rst @@ -1033,7 +1033,7 @@ Driver options For the MARK action the last 16 values in the full range are reserved for internal PMD purposes (to emulate FLAG action). The valid range for the - MARK action values is 0-0xFFEF for the 16-bit mode and 0-xFFFFEF + MARK action values is 0-0xFFEF for the 16-bit mode and 0-0xFFFFEF for the 24-bit mode, the flows with the MARK action value outside the specified range will be rejected. -- 2.27.0