From: Paolo Abeni <pabeni@redhat.com>
To: Simon Horman <horms@kernel.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
andrew+netdev@lunn.ch, netdev@vger.kernel.org
Subject: Re: [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2026-06-09 (idpf, ixgbe, igc)
Date: Sat, 13 Jun 2026 11:49:42 +0200 [thread overview]
Message-ID: <7ede2980-e7ac-4311-99af-5cca54841f36@redhat.com> (raw)
In-Reply-To: <20260612120309.GA671640@horms.kernel.org>
On 6/12/26 2:03 PM, Simon Horman wrote:
> On Tue, Jun 09, 2026 at 10:24:53AM -0700, Tony Nguyen wrote:
>> Przemyslaw adds needed padding to idpf PTP structures to match firmware
>> expectations.
>>
>> Larysa bypasses XPS configuration on XDP queues for ixgbe.
>>
>> Khai Wen corrects offset into packet buffer when handling for frame
>> preemption on igc.
>
> Hi Tony, Przemyslaw, and KhaiWenTan,
>
> There is AI-generated review of this patch-set available on both
> https://sashiko.dev and https://netdev-ai.bots.linux.dev/sashiko/
>
> I would appreciate it if you could look over the AI-generated review of
> patches 1 and 3.
Going over such comments looks like pre-existing issues or things better
handled as follow-up.
/P
next prev parent reply other threads:[~2026-06-13 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 17:24 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2026-06-09 (idpf, ixgbe, igc) Tony Nguyen
2026-06-09 17:24 ` [PATCH net 1/3] idpf: add padding to PTP virtchnl structures Tony Nguyen
2026-06-09 17:24 ` [PATCH net 2/3] ixgbe: do not configure xps for XDP queues Tony Nguyen
2026-06-09 17:24 ` [PATCH net 3/3] igc: skip RX timestamp header for frame preemption verification Tony Nguyen
2026-06-12 12:03 ` [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2026-06-09 (idpf, ixgbe, igc) Simon Horman
2026-06-13 9:49 ` Paolo Abeni [this message]
2026-06-13 10:00 ` patchwork-bot+netdevbpf
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=7ede2980-e7ac-4311-99af-5cca54841f36@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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