[PATCH v2] net/iavf: fix txq flags setting after Tx path selection

[Bruce Richardson]

On Mon, Feb 16, 2026 at 10:22:53AM +0000, Ciara Loftus wrote:
> Ensure the txq flags "use_ctx" and "use_vec_entry" are set/unset
> properly after tx path selection. Prior to this commit these flags were
> only configured if a vector path was chosen. Fix this by making their
> configuration unconditional. Also simplify how the "use_vec_entry" flag
> is set by removing the dedicated function that sets the flag in favour
> of just setting it inline.
> 
> Fixes: ebcfb039afa8 ("net/iavf: use common Tx path selection infrastructure")
> 
> Signed-off-by: Ciara Loftus <ciara.loftus at intel.com>
> Acked-by: Bruce Richardson <bruce.richardson at intel.com>
> ---
> v2:
> * Get a pointer to the selected tx path features and use it instead of
>  directly referencing it twice in a row.
> * Use >= SIMD_128 instead of != 0 to determine if a selected path is
>  vector (future proofing).
> ---
Applied to dpdk-next-net-intel,

Thanks,
/Bruce