Netdev List
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <davem@davemloft.net>, <pabeni@redhat.com>, <edumazet@kernel.org>,
	<andrew+netdev@lunn.ch>, <netdev@vger.kernel.org>,
	<florian.bezdeka@siemens.com>, <meng.ding@siemens.com>,
	<p@1g4.org>, <tkusters@aweta.nl>, <jiayuan.chen@linux.dev>,
	<pulehui@huawei.com>
Subject: Re: [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2026-10-01 (igc, igb, e1000e)
Date: Thu, 8 Oct 2026 10:04:56 -0700	[thread overview]
Message-ID: <793c66e0-e672-4ca1-9757-069958f3084c@intel.com> (raw)
In-Reply-To: <20261007190210.388650bf@kernel.org>



On 10/7/2026 7:02 PM, Jakub Kicinski wrote:
> On Thu,  1 Oct 2026 15:24:33 -0700 Tony Nguyen wrote:
>> For igc:
>> Ding Meng fixes Rx hardware timestamp when NET_RX_BUSY_POLL is disabled
>> by populating the skb hardware timestamp from the NIC's Rx timestamp.
>>
>> Paul Moses limits timestamp-header stripping to the first buffer of
>> each packet, preventing continuation-buffer data from being truncated.
>>
>> For igb:
>> Tjerk Kusters does the same limiting of timestamp-header stripping for
>> the igb driver.
> 
> these 3 need to be reworked
> 
>> For e1000e:
>> Jiayuan Chen prevents MSI-X IRQ leaks in IRQ error path.
>>
>> Pu Lehui prevents out-of-bounds MMIO access by rejecting devices whose
>> BAR0 is smaller than 64 KB.
> 
> applied to net-next
> 
>> Tony adds Lenovo ThinkPad P14s to disable list for K1 to avoid reported
>> issues with K1 re-enablement.
> 
> applied to net

Ok thanks Jakub.

- Tony

  reply	other threads:[~2026-10-08 17:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 22:24 [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2026-10-01 (igc, igb, e1000e) Tony Nguyen
2026-10-01 22:24 ` [PATCH net 1/6] igc: Fix RX HW timestamp reporting when NET_RX_BUSY_POLL is disabled Tony Nguyen
2026-10-05 23:02   ` netdev-bot+sashiko
2026-10-08  1:57   ` Jakub Kicinski
2026-10-01 22:24 ` [PATCH net 2/6] igc: only strip RX timestamp header from first buffer Tony Nguyen
2026-10-05 23:02   ` netdev-bot+sashiko
2026-10-07 16:02     ` Paul Moses
2026-10-01 22:24 ` [PATCH net 3/6] igb: only strip Rx timestamp header on the first buffer of a frame Tony Nguyen
2026-10-05 23:02   ` netdev-bot+sashiko
2026-10-01 22:24 ` [PATCH net 4/6] e1000e: fix IRQ leak when request_irq() fails in e1000_request_msix() Tony Nguyen
2026-10-01 22:24 ` [PATCH net 5/6] e1000e: Fix out-of-bounds MMIO access by validating BAR0 size Tony Nguyen
2026-10-05 23:02   ` netdev-bot+sashiko
2026-10-01 22:24 ` [PATCH net 6/6] e1000e: add system to disable K1 list Tony Nguyen
2026-10-01 22:29 ` [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2026-10-01 (igc, igb, e1000e) netdev-bot+sinfo
2026-10-08  2:02 ` Jakub Kicinski
2026-10-08 17:04   ` Tony Nguyen [this message]
2026-10-08  2:10 ` patchwork-bot+netdevbpf
2026-10-08  2:10 ` 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=793c66e0-e672-4ca1-9757-069958f3084c@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=florian.bezdeka@siemens.com \
    --cc=jiayuan.chen@linux.dev \
    --cc=kuba@kernel.org \
    --cc=meng.ding@siemens.com \
    --cc=netdev@vger.kernel.org \
    --cc=p@1g4.org \
    --cc=pabeni@redhat.com \
    --cc=pulehui@huawei.com \
    --cc=tkusters@aweta.nl \
    /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