netdev - Re: [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU traffic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z45iMxA6bBMoLSQ5@boxer>
Date: Mon, 20 Jan 2025 15:48:19 +0100
From: Maciej Fijalkowski <maciej.fijalkowski@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <intel-wired-lan@...ts.osuosl.org>, <netdev@...r.kernel.org>,
	<anthony.l.nguyen@...el.com>, <magnus.karlsson@...el.com>,
	<jacob.e.keller@...el.com>, <xudu@...hat.com>, <mschmidt@...hat.com>,
	<jmaxwell@...hat.com>, <poros@...hat.com>, <przemyslaw.kitszel@...el.com>
Subject: Re: [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU
 traffic

On Fri, Jan 17, 2025 at 01:22:08PM -0800, Jakub Kicinski wrote:
> On Fri, 17 Jan 2025 16:18:57 +0100 Maciej Fijalkowski wrote:
> > Subject: [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU traffic
> 
> nit: could you use iwl-net and iwl-next as the tree names?
> That's what we match on in NIPA to categorize Intel patches.

Not sure how I came up with my very own tree target. Will send a v3 then.