From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
To: dsosnowski@nvidia.com
Cc: dev@dpdk.org, rasland@nvidia.com, stable@dpdk.org,
viacheslavo@nvidia.com, bingz@nvidia.com, orika@nvidia.com,
suanmingm@nvidia.com, matan@nvidia.com
Subject: Re: [PATCH] doc/mlx5: document firmware requirement for flex item
Date: Tue, 22 Jul 2025 04:48:27 -0400 [thread overview]
Message-ID: <20250722084827.1309401-1-14pwcse1224@uetpeshawar.edu.pk> (raw)
In-Reply-To: <20250721132120.x5knqldvshgfwjl6@ds-vm-debian.local>
Hi,
Thank you for the clarification.
I was using this flex item configuration to offload a custom header to the NIC and apply match/action rules.
Looking forward to the PMD fix and the improved documentation.
Thanks again for investigating and clarifying the firmware requirements.
Best regards,
Khadem Ullah
prev parent reply other threads:[~2025-07-22 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 11:49 Khadem Ullah
2025-07-15 12:52 ` Dariusz Sosnowski
2025-07-16 7:49 ` Khadem Ullah
2025-07-21 13:21 ` Dariusz Sosnowski
2025-07-22 8:48 ` Khadem Ullah [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250722084827.1309401-1-14pwcse1224@uetpeshawar.edu.pk \
--to=14pwcse1224@uetpeshawar.edu.pk \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).