[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d9fd12f1-a858-c67e-b17f-2299bba9b17c@intel.com>
Date: Tue, 13 Jun 2023 09:23:19 -0700
From: Tony Nguyen <anthony.l.nguyen@...el.com>
To: Alexander Lobakin <aleksander.lobakin@...el.com>, Pavan Kumar Linga
<pavan.kumar.linga@...el.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Eric Dumazet
<edumazet@...gle.com>, <intel-wired-lan@...ts.osuosl.org>, Jakub Kicinski
<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, "David S. Miller"
<davem@...emloft.net>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v7 00/15] Introduce Intel IDPF
driver
On 6/13/2023 4:47 AM, Alexander Lobakin wrote:
> From: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
> Date: Mon, 12 Jun 2023 16:10:06 -0700
>
>> This patch series introduces the Intel(R) Infrastructure Data Path Function
>> (IDPF) driver. It is used for both physical and virtual functions. Except
>
> No netdev maintainers and generic MLs, not speaking that the previous
> versions already were there? What?
This was something I told Pavan he could do as this likely will be
turned around as the v2 PR. I was trying to save some extra thrash of,
nearly identical, iwl-next v7 and net-next v2 being sent in a short
timespan.
Thanks,
Tony
Powered by blists - more mailing lists