[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250528173909.41acd7f1@kernel.org>
Date: Wed, 28 May 2025 17:39:09 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Mina Almasry <almasrymina@...gle.com>
Cc: Pranjal Shrivastava <praan@...gle.com>, netdev@...r.kernel.org, "David S
. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Simon
Horman <horms@...nel.org>, Willem de Bruijn <willemb@...gle.com>, Kaiyuan
Zhang <kaiyuanz@...gle.com>
Subject: Re: [PATCH net-next] net: Fix net_devmem_bind_dmabuf for non-devmem
configs
On Wed, 28 May 2025 14:53:35 -0700 Mina Almasry wrote:
> I'm unsure whether this needs to be resent to net now or wait for the
> merge window to reopen. I think net is for fixes to code in mainline
> linux, but the devmem TX path has not made it there yet (and is not
> even in the net tree yet). My guess is that this patch should be
> reposted to net-next once net-next reopens.
net-next "becomes" net during the merge window.
There's a period of tree-uncertainty while our PR is out,
and afterwards all fixes should target net.
No need to repost, we'll take this fix in tomorrow.
Powered by blists - more mailing lists