From: Bruce Richardson <bruce.richardson@intel.com>
To: Shaiq Wani <shaiq.wani@intel.com>
Cc: <dev@dpdk.org>, <aman.deep.singh@intel.com>
Subject: Re: [PATCH v1 2/2] doc: update recommended matching list for idpf PMD
Date: Wed, 18 Jun 2025 14:32:23 +0100 [thread overview]
Message-ID: <aFK_5wfbp-ukV5Ij@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250612122543.146876-3-shaiq.wani@intel.com>
On Thu, Jun 12, 2025 at 05:55:43PM +0530, Shaiq Wani wrote:
> Updated the recommended MEV-ts release versions corresponding to DPDK
> releases in the idpf driver documentation.
>
> Signed-off-by: Shaiq Wani <shaiq.wani@intel.com> ---
> doc/guides/nics/idpf.rst | 2 ++ 1 file changed, 2 insertions(+)
>
> diff --git a/doc/guides/nics/idpf.rst b/doc/guides/nics/idpf.rst index
> b55de3abd3..3d694a4e3e 100644 --- a/doc/guides/nics/idpf.rst +++
> b/doc/guides/nics/idpf.rst @@ -33,6 +33,8 @@ Here is the suggested
> matching list which has been tested and verified.
> +------------+---------------+------------------+ | 23.11 |
> 0.0.720 | 1.0 |
> +------------+---------------+------------------+ + | 25.07 |
> 0.0.754 | 2.0 | +
> +------------+---------------+------------------+
>
>
There is a big time gap in this series. Is it worth doing up a new version
of the patch, with an intermediate value added? For example, what is the
recommended version to match 24.11 LTS?
/Bruce
prev parent reply other threads:[~2025-06-18 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 12:13 [PATCH 1/2] doc: update recommended matching list for cpfl PMD Shaiq Wani
2025-06-12 12:13 ` [PATCH 2/2] doc: update recommended matching list for idpf PMD Shaiq Wani
2025-06-12 12:25 ` [PATCH v1 0/2] doc: update recommended matching list Shaiq Wani
2025-06-12 12:25 ` [PATCH v1 1/2] doc: update recommended matching list for cpfl PMD Shaiq Wani
2025-06-12 12:25 ` [PATCH v1 2/2] doc: update recommended matching list for idpf PMD Shaiq Wani
2025-06-18 13:32 ` Bruce Richardson [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=aFK_5wfbp-ukV5Ij@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=shaiq.wani@intel.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).