public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, andrew+netdev@lunn.ch,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/7][pull request] Intel Wired LAN Driver Updates 2026-01-26 (ice, idpf)
Date: Wed, 28 Jan 2026 01:40:23 +0000	[thread overview]
Message-ID: <176956442310.1470424.275510766558501876.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260126224313.3847849-1-anthony.l.nguyen@intel.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:

On Mon, 26 Jan 2026 14:43:04 -0800 you wrote:
> For ice:
> Jake converts ring stats to utilize u64_stats APIs and performs some
> cleanups along the way.
> 
> Alexander reorganizes layout of Tx and Rx rings for cacheline
> locality and utilizes __cacheline_group* macros on the new layouts.
> 
> [...]

Here is the summary with links:
  - [net-next,1/7] ice: pass pointer to ice_fetch_u64_stats_per_ring
    https://git.kernel.org/netdev/net-next/c/fb5b8f3c8870
  - [net-next,2/7] ice: remove ice_q_stats struct and use struct_group
    https://git.kernel.org/netdev/net-next/c/b470944ee6e8
  - [net-next,3/7] ice: use u64_stats API to access pkts/bytes in dim sample
    https://git.kernel.org/netdev/net-next/c/b1c16d9cb21e
  - [net-next,4/7] ice: shorten ring stat names and add accessors
    https://git.kernel.org/netdev/net-next/c/4c58c7152c09
  - [net-next,5/7] ice: convert all ring stats to u64_stats_t
    https://git.kernel.org/netdev/net-next/c/b38a418db366
  - [net-next,6/7] ice: reshuffle and group Rx and Tx queue fields by cachelines
    https://git.kernel.org/netdev/net-next/c/24f90786efaf
  - [net-next,7/7] idpf: export RX hardware timestamping information to XDP
    https://git.kernel.org/netdev/net-next/c/13a4be41261f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-01-28  1:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 22:43 [PATCH net-next 0/7][pull request] Intel Wired LAN Driver Updates 2026-01-26 (ice, idpf) Tony Nguyen
2026-01-26 22:43 ` [PATCH net-next 1/7] ice: pass pointer to ice_fetch_u64_stats_per_ring Tony Nguyen
2026-01-26 22:43 ` [PATCH net-next 2/7] ice: remove ice_q_stats struct and use struct_group Tony Nguyen
2026-01-26 22:43 ` [PATCH net-next 3/7] ice: use u64_stats API to access pkts/bytes in dim sample Tony Nguyen
2026-01-26 22:43 ` [PATCH net-next 4/7] ice: shorten ring stat names and add accessors Tony Nguyen
2026-01-26 22:43 ` [PATCH net-next 5/7] ice: convert all ring stats to u64_stats_t Tony Nguyen
2026-01-26 22:43 ` [PATCH net-next 6/7] ice: reshuffle and group Rx and Tx queue fields by cachelines Tony Nguyen
2026-01-26 22:43 ` [PATCH net-next 7/7] idpf: export RX hardware timestamping information to XDP Tony Nguyen
2026-01-28  1:40 ` patchwork-bot+netdevbpf [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=176956442310.1470424.275510766558501876.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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