netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Mina Almasry <almasrymina@google.com>
Cc: Pranjal Shrivastava <praan@google.com>,
	netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Simon Horman <horms@kernel.org>,
	Willem de Bruijn <willemb@google.com>,
	Kaiyuan Zhang <kaiyuanz@google.com>
Subject: Re: [PATCH net-next] net: Fix net_devmem_bind_dmabuf for non-devmem configs
Date: Wed, 28 May 2025 17:39:09 -0700	[thread overview]
Message-ID: <20250528173909.41acd7f1@kernel.org> (raw)
In-Reply-To: <CAHS8izO=64PCgs7mjobznH0D7sQ76fBXjWoTTNxzO-Or+hqhcQ@mail.gmail.com>

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.

  reply	other threads:[~2025-05-29  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 21:10 [PATCH net-next] net: Fix net_devmem_bind_dmabuf for non-devmem configs Pranjal Shrivastava
2025-05-28 21:53 ` Mina Almasry
2025-05-29  0:39   ` Jakub Kicinski [this message]
2025-05-31  2:40 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250528173909.41acd7f1@kernel.org \
    --to=kuba@kernel.org \
    --cc=almasrymina@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kaiyuanz@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=praan@google.com \
    --cc=willemb@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).