patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Andrew Boyer <andrew.boyer@amd.com>
Cc: dpdk stable <stable@dpdk.org>, Luca Boccassi <bluca@debian.org>,
	Shani Peretz <shperetz@nvidia.com>
Subject: Re: patch 'doc: add Pollara 400 device in ionic guide' has been queued to stable release 24.11.4
Date: Tue, 25 Nov 2025 15:13:59 +0000	[thread overview]
Message-ID: <8b2f1a05-9ddd-4358-bf4b-345888a0b2e6@redhat.com> (raw)
In-Reply-To: <20251125150558.232595-5-ktraynor@redhat.com>

On 25/11/2025 15:05, Kevin Traynor wrote:
> Hi,
> 
> FYI, your patch has been queued to stable release 24.11.4
> 
> Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
> It will be pushed if I get no objections before 11/28/25. So please
> shout if anyone has objections.
> 
> Also note that after the patch there's a diff of the upstream commit vs the
> patch applied to the branch. This will indicate if there was any rebasing
> needed to apply to the stable branch. If there were code changes for rebasing
> (ie: not only metadata diffs), please double check that the rebase was
> correctly done.
> 
> Queued patches are on a temporary branch at:
> https://github.com/kevintraynor/dpdk-stable
> 
> This queued commit can be viewed at:
> https://github.com/kevintraynor/dpdk-stable/commit/96bbffc68b4eccccc8a1d9977fc85ee9b139c527
> 

Hi Andrew,

I prepared this for the 24.11 branch as it is marked for stable and
24.11 is the current latest LTS branch.

Can you confirm which of the LTS branches this is applicable to ?
22.11, 23.11 and 24.11 are the maintained LTS branches.

thanks,
Kevin.

> Thanks.
> 
> Kevin
> 
> ---
>>From 96bbffc68b4eccccc8a1d9977fc85ee9b139c527 Mon Sep 17 00:00:00 2001
> From: Andrew Boyer <andrew.boyer@amd.com>
> Date: Thu, 20 Nov 2025 10:39:36 -0800
> Subject: [PATCH] doc: add Pollara 400 device in ionic guide
> 
> [ upstream commit 899e7bb0ab84a31a36437e8ad6e40493eea4b0ef ]
> 
> The Pollara 400 AI NIC is supported without any PMD changes.
> Add a link to the product brief.
> 
> Signed-off-by: Andrew Boyer <andrew.boyer@amd.com>
> ---
>  doc/guides/cryptodevs/ionic.rst | 4 +++-
>  doc/guides/nics/ionic.rst       | 4 +++-
>  2 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/guides/cryptodevs/ionic.rst b/doc/guides/cryptodevs/ionic.rst
> index d563602ebe..7c9d2ebd04 100644
> --- a/doc/guides/cryptodevs/ionic.rst
> +++ b/doc/guides/cryptodevs/ionic.rst
> @@ -1,4 +1,4 @@
>  .. SPDX-License-Identifier: BSD-3-Clause
> -   Copyright 2021-2024 Advanced Micro Devices, Inc.
> +   Copyright 2021-2025 Advanced Micro Devices, Inc.
>  
>  IONIC Crypto Driver
> @@ -17,4 +17,6 @@ It currently supports the below models:
>  - DSC3-400 dual-port 400G Distributed Services Card
>    `(pdf) <https://www.amd.com/content/dam/amd/en/documents/pensando-technical-docs/product-briefs/pensando-dsc3-product-brief.pdf>`__
> +- Pollara 400 single-port 400G AI NIC
> +  `(pdf) <https://www.amd.com/content/dam/amd/en/documents/pensando-technical-docs/product-briefs/pollara-product-brief.pdf>`__
>  
>  Please visit the
> diff --git a/doc/guides/nics/ionic.rst b/doc/guides/nics/ionic.rst
> index a991a2cf3f..2709a888fb 100644
> --- a/doc/guides/nics/ionic.rst
> +++ b/doc/guides/nics/ionic.rst
> @@ -1,4 +1,4 @@
>  ..  SPDX-License-Identifier: BSD-3-Clause
> -    Copyright 2018-2022 Advanced Micro Devices, Inc.
> +    Copyright 2018-2025 Advanced Micro Devices, Inc.
>  
>  IONIC Driver
> @@ -16,4 +16,6 @@ It currently supports the below models:
>  - DSC3-400 dual-port 400G Distributed Services Card
>    `(pdf) <https://www.amd.com/content/dam/amd/en/documents/pensando-technical-docs/product-briefs/pensando-dsc3-product-brief.pdf>`__
> +- Pollara 400 single-port 400G AI NIC
> +  `(pdf) <https://www.amd.com/content/dam/amd/en/documents/pensando-technical-docs/product-briefs/pollara-product-brief.pdf>`__
>  
>  Please visit the


  reply	other threads:[~2025-11-25 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 15:05 patch 'examples/l3fwd: add Tx burst size configuration option' " Kevin Traynor
2025-11-25 15:05 ` patch 'examples/server_node_efd: fix format overflow' " Kevin Traynor
2025-11-25 15:05 ` patch 'examples/vdpa: " Kevin Traynor
2025-11-25 15:05 ` patch 'net/mlx5: fix flex flow item header length' " Kevin Traynor
2025-11-25 15:05 ` patch 'doc: add Pollara 400 device in ionic guide' " Kevin Traynor
2025-11-25 15:13   ` Kevin Traynor [this message]
2025-11-25 15:26     ` Boyer, Andrew
2025-11-25 15:05 ` patch 'doc: fix note in FreeBSD " Kevin Traynor
2025-11-26 11:08 ` patch 'examples/l3fwd: add Tx burst size configuration option' " Kevin Traynor
2025-11-26 11:19   ` Ande, Venkat Kumar
2025-11-26 11:51     ` Kevin Traynor

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=8b2f1a05-9ddd-4358-bf4b-345888a0b2e6@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=andrew.boyer@amd.com \
    --cc=bluca@debian.org \
    --cc=shperetz@nvidia.com \
    --cc=stable@dpdk.org \
    /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).