DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Soumyadeep Hore <soumyadeep.hore@intel.com>
Cc: <manoj.kumar.subbarao@intel.com>, <aman.deep.singh@intel.com>,
	<dev@dpdk.org>
Subject: Re: [PATCH v1 2/2] doc: update recommended matching versions for cpfl and idpf
Date: Tue, 19 May 2026 18:05:38 +0100	[thread overview]
Message-ID: <agyYYj_wSrSRDpCJ@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260509015408.29188-3-soumyadeep.hore@intel.com>

On Fri, May 08, 2026 at 09:54:08PM -0400, Soumyadeep Hore wrote:
> Update the recommended MEV-ts release version corresponding to DPDK
> release in the cpfl and idpf drivers documentation.
> 
> Signed-off-by: Soumyadeep Hore <soumyadeep.hore@intel.com>
> ---
>  doc/guides/nics/cpfl.rst | 2 ++
>  doc/guides/nics/idpf.rst | 2 ++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/doc/guides/nics/cpfl.rst b/doc/guides/nics/cpfl.rst
> index bc42c524ea..da884f5e3b 100644
> --- a/doc/guides/nics/cpfl.rst
> +++ b/doc/guides/nics/cpfl.rst
> @@ -41,6 +41,8 @@ Here is the suggested matching list which has been tested and verified.
>     +------------+------------------+
>     |    25.07   |       2.0        |
>     +------------+------------------+
> +   |    26.07   |       2.2        |
> +   +------------+------------------+
>  

This is strange, having just the .07 releases listed in the table. Is the
same version for 25.07 applicable for 25.11? Perhaps we can update the
table to cover that, so that only LTS versions are listed apart from the
latest release.

Other feedback, to help align with e.g. tables in ice and i40e drivers.
This is not mandatory for this patch, but it would be nice to have IMHO:

* list only LTS releases (i.e. remove 23.07)
* list releases in descending order, so that latest is on top
* rework table to use the new RST table format (see ice.rst for example).

Regards,
/Bruce
>  
>  Configuration
> diff --git a/doc/guides/nics/idpf.rst b/doc/guides/nics/idpf.rst
> index c7c76190c8..a6f611c09b 100644
> --- a/doc/guides/nics/idpf.rst
> +++ b/doc/guides/nics/idpf.rst
> @@ -37,6 +37,8 @@ Here is the suggested matching list which has been tested and verified.
>     +------------+---------------+------------------+
>     |    25.07   |    0.0.772    |       2.0        |
>     +------------+---------------+------------------+
> +   |    26.07   |    0.0.780    |       2.2        |
> +   +------------+---------------+------------------+
>  
>  
>  Configuration
> -- 
> 2.47.1
> 

  reply	other threads:[~2026-05-19 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09  1:54 [PATCH v1 0/2] Update IDPF Base Code Soumyadeep Hore
2026-05-09  1:54 ` [PATCH v1 1/2] net/idpf/base: add MMG device IDs Soumyadeep Hore
2026-05-09  1:54 ` [PATCH v1 2/2] doc: update recommended matching versions for cpfl and idpf Soumyadeep Hore
2026-05-19 17:05   ` Bruce Richardson [this message]
2026-05-20 22:03   ` [PATCH v2 0/2] Update IDPF Base Code Soumyadeep Hore
2026-05-20 22:03     ` [PATCH v2 1/2] net/idpf/base: add MMG device IDs Soumyadeep Hore
2026-05-20 22:03     ` [PATCH v2 2/2] doc: update recommended matching versions for cpfl and idpf Soumyadeep Hore
2026-05-22 15:09     ` [PATCH v2 0/2] Update IDPF Base Code Bruce Richardson

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=agyYYj_wSrSRDpCJ@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=manoj.kumar.subbarao@intel.com \
    --cc=soumyadeep.hore@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