[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241007082851.0de5e329@kernel.org>
Date: Mon, 7 Oct 2024 08:28:51 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Rosen Penev <rosenp@...il.com>
Cc: netdev@...r.kernel.org, andrew@...n.ch, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, linux-kernel@...r.kernel.org,
jacob.e.keller@...el.com, horms@...nel.org, sd@...asysnail.net,
chunkeey@...il.com
Subject: Re: [PATCH net-next v3 17/17] net: ibm: emac: mal: move dcr map
down
On Mon, 7 Oct 2024 07:05:14 -0700 Jakub Kicinski wrote:
> > > Not a fix?
> > It's a fix for a prior commit, yes. 6d3ba097ee81d if I'm using git
> > blame correctly.
>
> Hm, I don't have this hash in my local tree.
> What I'm getting at is that if it's a fix for a patch already in
> networking trees the patch needs to have a Fixes tag. And if the
> bug is present in net - the patch needs to go to net rather than
> net-next.
Looking closer I think this got added in:
commit 1ff0fcfcb1a6 ("ibm_newemac: Fix new MAL feature handling")
please post the first to net. Then once net gets merged to net-next
(which happens every Thu), you can proceed with the net-next
conversions.
Powered by blists - more mailing lists