From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>, <dev@dpdk.org>
Cc: <bruce.richardson@intel.com>
Subject: Re: [PATCH 0/9] Update ICE base driver
Date: Fri, 23 Oct 2026 12:17:25 +0200 [thread overview]
Message-ID: <25893dcd-99b0-44d0-a9dc-2947f2da59f8@intel.com> (raw)
In-Reply-To: <20261022165205.1830735-1-vladimir.medvedkin@intel.com>
On 10/22/2026 6:51 PM, Vladimir Medvedkin wrote:
> Update the ICE base driver to the latest shared code snapshot:
>
> - Bounds check, integer overflow and type fixes
> - New capability and NVM definitions
> - New E835 10GBASE-T device ID
>
> Chinh Cao (2):
> net/ice/base: add NVM definitions for Wake-on-LAN config
> net/ice/base: add E835 10GBASE-T device ID
>
> Deepthi Kavalur (1):
> net/ice/base: fix loop counter type in recipe creation
>
> Janardhanan Arumugam (1):
> net/ice/base: fix out-of-bounds accesses in DDP and NVM code
>
> Krzysztof Galazka (1):
> net/ice/base: fix integer overflow in RL profile calculation
>
> Przemyslaw Gierszynski (1):
> net/ice/base: add RDE WoL override capability bit
>
> Stefan Wegrzyn (2):
> net/ice/base: add PQC certificate provisioning capability
> net/ice/base: add NVM write flags for eRoT minSREV update
>
> Vladimir Medvedkin (1):
> net/ice/base: update version info
>
> drivers/net/intel/ice/base/README | 2 +-
> drivers/net/intel/ice/base/ice_adminq_cmd.h | 6 ++++++
> drivers/net/intel/ice/base/ice_common.c | 6 ++++++
> drivers/net/intel/ice/base/ice_ddp.c | 19 ++++++++++++-------
> drivers/net/intel/ice/base/ice_devids.h | 14 ++++++++------
> drivers/net/intel/ice/base/ice_nvm.c | 4 ++--
> drivers/net/intel/ice/base/ice_sched.c | 18 ++++++++----------
> drivers/net/intel/ice/base/ice_switch.c | 2 +-
> drivers/net/intel/ice/base/ice_type.h | 16 +++++++++++++++-
> drivers/net/intel/ice/ice_ethdev.c | 1 +
> 10 files changed, 60 insertions(+), 28 deletions(-)
>
Series-acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2026-10-23 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 16:51 [PATCH 0/9] Update ICE base driver Vladimir Medvedkin
2026-10-22 16:51 ` [PATCH 1/9] net/ice/base: fix loop counter type in recipe creation Vladimir Medvedkin
2026-10-22 16:51 ` [PATCH 2/9] net/ice/base: fix integer overflow in RL profile calculation Vladimir Medvedkin
2026-10-22 16:51 ` [PATCH 3/9] net/ice/base: fix out-of-bounds accesses in DDP and NVM code Vladimir Medvedkin
2026-10-22 16:52 ` [PATCH 4/9] net/ice/base: add PQC certificate provisioning capability Vladimir Medvedkin
2026-10-22 16:52 ` [PATCH 5/9] net/ice/base: add NVM definitions for Wake-on-LAN config Vladimir Medvedkin
2026-10-22 16:52 ` [PATCH 6/9] net/ice/base: add NVM write flags for eRoT minSREV update Vladimir Medvedkin
2026-10-22 16:52 ` [PATCH 7/9] net/ice/base: add RDE WoL override capability bit Vladimir Medvedkin
2026-10-22 16:52 ` [PATCH 8/9] net/ice/base: add E835 10GBASE-T device ID Vladimir Medvedkin
2026-10-22 16:52 ` [PATCH 9/9] net/ice/base: update version info Vladimir Medvedkin
2026-10-23 10:17 ` Burakov, Anatoly [this message]
2026-10-23 13:56 ` [PATCH 0/9] Update ICE base driver Bruce Richardson
2026-10-23 10:39 ` Bruce Richardson
2026-10-23 13:00 ` Medvedkin, Vladimir
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=25893dcd-99b0-44d0-a9dc-2947f2da59f8@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=vladimir.medvedkin@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