From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
anthony.l.nguyen@intel.com, joshua.a.hay@intel.com,
przemyslaw.kitszel@intel.com,
Willem de Bruijn <willemb@google.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 0/6] hardware pacing offload
Date: Fri, 07 Aug 2026 19:47:14 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.342b45ed25289@gmail.com> (raw)
In-Reply-To: <20260807153933.7b8b01d4@kernel.org>
Jakub Kicinski wrote:
> On Thu, 06 Aug 2026 21:18:37 -0400 Willem de Bruijn wrote:
> > This was intended to have a wider audience list. Will address in v5.
>
> LGTM FWIW
Good to know thanks!
I will fix up a kdoc warning that patchwork pointed out.
WARNING: multiple messages have this Message-ID (diff)
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
anthony.l.nguyen@intel.com, joshua.a.hay@intel.com,
przemyslaw.kitszel@intel.com,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next v4 0/6] hardware pacing offload
Date: Fri, 07 Aug 2026 19:47:14 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.342b45ed25289@gmail.com> (raw)
In-Reply-To: <20260807153933.7b8b01d4@kernel.org>
Jakub Kicinski wrote:
> On Thu, 06 Aug 2026 21:18:37 -0400 Willem de Bruijn wrote:
> > This was intended to have a wider audience list. Will address in v5.
>
> LGTM FWIW
Good to know thanks!
I will fix up a kdoc warning that patchwork pointed out.
next prev parent reply other threads:[~2026-08-07 23:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 23:25 [Intel-wired-lan] [PATCH net-next v4 0/6] hardware pacing offload Willem de Bruijn
2026-08-06 23:25 ` Willem de Bruijn
2026-08-06 23:25 ` [Intel-wired-lan] [PATCH net-next v4 1/6] net: rtnetlink: add pacing_offload_horizon attribute to net_device Willem de Bruijn
2026-08-06 23:25 ` Willem de Bruijn
2026-08-06 23:25 ` [Intel-wired-lan] [PATCH net-next v4 2/6] net_sched: sch_fq: clear past skb->tstamp if offloading pacing Willem de Bruijn
2026-08-06 23:25 ` Willem de Bruijn
2026-08-06 23:26 ` [Intel-wired-lan] [PATCH net-next v4 3/6] idpf: support pacing offload Willem de Bruijn
2026-08-06 23:26 ` Willem de Bruijn
2026-08-06 23:26 ` [Intel-wired-lan] [PATCH net-next v4 4/6] selftests: drv-net: refactor so_txtime errqueue handling Willem de Bruijn
2026-08-06 23:26 ` Willem de Bruijn
2026-08-06 23:26 ` [Intel-wired-lan] [PATCH net-next v4 5/6] selftests: drv-net: in so_txtime tell apart sw from hw pacing Willem de Bruijn
2026-08-06 23:26 ` Willem de Bruijn
2026-08-06 23:26 ` [Intel-wired-lan] [PATCH net-next v4 6/6] selftests: drv-net: extend so_txtime with hw offload Willem de Bruijn
2026-08-06 23:26 ` Willem de Bruijn
2026-08-07 1:18 ` [Intel-wired-lan] [PATCH net-next v4 0/6] hardware pacing offload Willem de Bruijn
2026-08-07 1:18 ` Willem de Bruijn
2026-08-07 22:39 ` [Intel-wired-lan] " Jakub Kicinski
2026-08-07 22:39 ` Jakub Kicinski
2026-08-07 23:47 ` Willem de Bruijn [this message]
2026-08-07 23:47 ` Willem de Bruijn
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=willemdebruijn.kernel.342b45ed25289@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.