[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <IA3PR11MB8986716738B85D0CEF52EAD2E599A@IA3PR11MB8986.namprd11.prod.outlook.com>
Date: Thu, 5 Feb 2026 08:33:22 +0000
From: "Loktionov, Aleksandr" <aleksandr.loktionov@...el.com>
To: Ethan Nelson-Moore <enelsonmoore@...il.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>, "Johannes
Berg" <johannes@...solutions.net>, "stable@...r.kernel.org"
<stable@...r.kernel.org>, "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@...el.com>, Andrew Lunn
<andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, "Eric
Dumazet" <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Stanislav Yakovlev <stas.yakovlev@...il.com>, "Alice
Michael" <alice.michael@...el.com>
Subject: RE: [PATCH net-next] net: intel: fix PCI device ID conflict between
i40e and ipw2200
> -----Original Message-----
> From: Ethan Nelson-Moore <enelsonmoore@...il.com>
> Sent: Thursday, February 5, 2026 9:18 AM
> To: Loktionov, Aleksandr <aleksandr.loktionov@...el.com>
> Cc: netdev@...r.kernel.org; linux-wireless@...r.kernel.org; Johannes
> Berg <johannes@...solutions.net>; stable@...r.kernel.org; Nguyen,
> Anthony L <anthony.l.nguyen@...el.com>; Kitszel, Przemyslaw
> <przemyslaw.kitszel@...el.com>; Andrew Lunn <andrew+netdev@...n.ch>;
> David S. Miller <davem@...emloft.net>; Eric Dumazet
> <edumazet@...gle.com>; Jakub Kicinski <kuba@...nel.org>; Paolo Abeni
> <pabeni@...hat.com>; Stanislav Yakovlev <stas.yakovlev@...il.com>;
> Alice Michael <alice.michael@...el.com>
> Subject: Re: [PATCH net-next] net: intel: fix PCI device ID conflict
> between i40e and ipw2200
>
> Hi, Alexandr,
>
> On Thu, Feb 5, 2026 at 12:13 AM Loktionov, Aleksandr
> <aleksandr.loktionov@...el.com> wrote:
> > Commit message could be more detailed.
> > - Why the PCI ID is being reused (if known) Is this actually a reuse
> after EOL, or is there a misunderstanding? The commit message hand-
> waves this critical detail.
> > - Whether this is documented in hardware datasheets
> > - If there are bug reports of the conflict in the wild
> I don't know any of this information. I found this conflict via a
> script I was motivated to write by noticing an ID conflict between
> r8169 and 8139too.
>
> > If it's quite critical fix why not to send it to [PATCH net] ?
> I used that prefix because the patch is against net-next. It will make
> it into stable versions regardless.
>
> Ethan
I thought 'fix' patches must go to net first, isn't it?
Powered by blists - more mailing lists