From: Bruce Richardson <bruce.richardson@intel.com>
To: Dhanya Pillai <dhanya.r.pillai@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v3 00/10] Update ice base code
Date: Thu, 29 May 2025 09:29:43 +0100 [thread overview]
Message-ID: <aDga96S6dMfzysGh@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250527131741.7606-1-dhanya.r.pillai@intel.com>
On Tue, May 27, 2025 at 01:17:19PM +0000, Dhanya Pillai wrote:
> ice base code is updated to latest snapshot.
>
> v3:
> - Fixed check patch failure in DPDK CI.
> - Added Fixes tag to bug fixes.
> - Corrected author name for couple of patches.
>
> v2:
> - Added Author Signoff.
>
> Dhanya Pillai (1):
> net/ice/base: update version info
>
> Janardhanan Arumugam (1):
> net/ice/base: increase reset timeout to 20 seconds
>
> Lukasz Krakowiak (3):
> net/ice/base: fix integer overflow issue
> net/ice/base: set speculative execution barrier
> net/ice/base: fix typo in desc for dev ID 579F
>
> Mikolaj Filar (2):
> net/ice/base: support for MAC rule with own filter flags
> net/ice/base: configure PHY FEC error in logs for GNRD
>
> Oleg Akhrem (1):
> net/ice/base: ptp minimal refactoring
>
> Paul Greenwalt (1):
> net/ice/base: fix typo in media type check
>
> Waldemar Dworakowski (1):
> net/ice/base: fix type conversion
>
> drivers/net/intel/ice/base/README | 2 +-
> drivers/net/intel/ice/base/ice_common.c | 6 ++-
> drivers/net/intel/ice/base/ice_devids.h | 2 +-
> drivers/net/intel/ice/base/ice_flex_pipe.c | 2 +
> drivers/net/intel/ice/base/ice_osdep.h | 6 +++
> drivers/net/intel/ice/base/ice_ptp_hw.c | 9 ++---
> drivers/net/intel/ice/base/ice_sched.c | 10 +++--
> drivers/net/intel/ice/base/ice_switch.c | 46 ++++++++++++++++++++--
> drivers/net/intel/ice/base/ice_switch.h | 1 +
> drivers/net/intel/ice/base/ice_type.h | 2 +-
> 10 files changed, 68 insertions(+), 18 deletions(-)
>
Series-acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied to dpdk-next-net-intel with the suggested changes.
Thanks,
/Bruce
prev parent reply other threads:[~2025-05-29 8:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 13:17 Dhanya Pillai
2025-05-27 13:17 ` [PATCH v3 01/10] net/ice/base: fix type conversion Dhanya Pillai
2025-05-27 16:54 ` Bruce Richardson
2025-05-27 13:17 ` [PATCH v3 02/10] net/ice/base: fix typo in media type check Dhanya Pillai
2025-05-27 13:17 ` [PATCH v3 03/10] net/ice/base: fix integer overflow issue Dhanya Pillai
2025-05-27 17:06 ` Bruce Richardson
2025-05-27 13:17 ` [PATCH v3 04/10] net/ice/base: set speculative execution barrier Dhanya Pillai
2025-05-28 13:07 ` Bruce Richardson
2025-05-28 14:59 ` Bruce Richardson
2025-05-28 17:55 ` Pillai, Dhanya R
2025-05-27 13:17 ` [PATCH v3 05/10] net/ice/base: fix typo in desc for dev ID 579F Dhanya Pillai
2025-05-27 13:17 ` [PATCH v3 06/10] net/ice/base: ptp minimal refactoring Dhanya Pillai
2025-05-27 13:17 ` [PATCH v3 07/10] net/ice/base: support for MAC rule with own filter flags Dhanya Pillai
2025-05-27 13:17 ` [PATCH v3 08/10] net/ice/base: configure PHY FEC error in logs for GNRD Dhanya Pillai
2025-05-27 13:17 ` [PATCH v3 09/10] net/ice/base: increase reset timeout to 20 seconds Dhanya Pillai
2025-05-27 13:17 ` [PATCH v3 10/10] net/ice/base: update version info Dhanya Pillai
2025-05-29 8:29 ` 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=aDga96S6dMfzysGh@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dhanya.r.pillai@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).