please help backporting some patches to stable release 23.11.1

[Xueming Li <xuemingl@nvidia.com>]

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 23.11
stable branch, as conflicts or build errors occur.

Can authors check your patches in the following list and either:
    - Backport your patches to the 23.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 04/20/24.

You can find the a temporary work-in-progress branch of the coming 23.11.1
release at:
    https://git.dpdk.org/dpdk-stable/log/?h=23.11-staging
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

Some notes on stable backports:

A backport should contain a reference to the DPDK main branch commit
in it's commit message in the following fashion:
    [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]

For example:
    https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 23.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 23.11'

Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".

FYI, branch 23.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Xueming Li <xuemingl@nvidia.com>

---
5ecc8df4fa  Dariusz Sosnowski net/mlx5: fix async flow create error handling
727283742a  Dariusz Sosnowski net/mlx5: fix rollback on failed flow configure
572fe9ef2f  Erez Shitrit     net/mlx5/hws: fix port ID for root table
ddc84b53f3  Long Wu          net/nfp: fix port ID meta data use in Rx
647a0a6ecb  Mingjin Ye       bus/pci: fix VFIO region info in secondary process
eb1dec5f5b  Mingjin Ye       net/iavf: fix null dereference