From: Jakub Kicinski <kuba@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Simon Schippers <simon.schippers@tu-dortmund.de>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowangio@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Tim Gebauer <tim.gebauer@tu-dortmund.de>,
Brett Sheffield <brett@librecast.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] tun/tap & vhost-net: make qdisc backpressure opt-in via IFF_BACKPRESSURE
Date: Wed, 22 Jul 2026 07:26:31 -0700 [thread overview]
Message-ID: <20260722072631.21b57e1e@kernel.org> (raw)
In-Reply-To: <20260722040722-mutt-send-email-mst@kernel.org>
On Wed, 22 Jul 2026 04:09:25 -0400 Michael S. Tsirkin wrote:
> > Would be great if you could do the revert.
> > I don't want to mess it up. :P
> >
> > For the re-apply:
> > I can post a v13 to net-next soon with the flag included
> > into the existing commits.
> > Or would you rather take v12 plus this opt-in commit as-is?
> >
> > Thanks!
>
> jacub if the revert goes into next what is the process to
> target a patch on top of it for net-next? Thanks!
misheal, revert will be merged to net and reach net-next on Thu after
the downstream PR, at which point you can post the net-next patch.
next prev parent reply other threads:[~2026-07-22 14:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 9:55 [PATCH net v3] tun/tap & vhost-net: make qdisc backpressure opt-in via IFF_BACKPRESSURE Simon Schippers
2026-07-09 16:06 ` Brett Sheffield
2026-07-14 6:57 ` Simon Schippers
2026-07-14 13:40 ` Michael S. Tsirkin
2026-07-14 16:50 ` Simon Schippers
2026-07-21 14:04 ` Simon Schippers
2026-07-21 14:59 ` Michael S. Tsirkin
2026-07-21 17:07 ` Jakub Kicinski
2026-07-22 6:07 ` Michael S. Tsirkin
2026-07-22 6:39 ` Simon Schippers
2026-07-22 8:09 ` Michael S. Tsirkin
2026-07-22 14:26 ` Jakub Kicinski [this message]
2026-07-15 14:01 ` kernel test robot
2026-07-15 14:32 ` Simon Schippers
2026-07-16 1:22 ` Oliver Sang
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=20260722072631.21b57e1e@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brett@librecast.net \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jasowangio@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.schippers@tu-dortmund.de \
--cc=skhan@linuxfoundation.org \
--cc=tim.gebauer@tu-dortmund.de \
--cc=willemdebruijn.kernel@gmail.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