From: Jakub Kicinski <kuba@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Jason Wang" <jasowang@redhat.com>,
netdev@vger.kernel.org, "Eugenio Pérez" <eperezma@redhat.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
virtualization@lists.linux.dev
Subject: Re: [PATCH net-next v1 0/4] virtio_net: enable premapped mode by default
Date: Wed, 6 Nov 2024 10:36:38 -0800 [thread overview]
Message-ID: <20241106103638.5844fe15@kernel.org> (raw)
In-Reply-To: <20241106041545-mutt-send-email-mst@kernel.org>
On Wed, 6 Nov 2024 04:16:07 -0500 Michael S. Tsirkin wrote:
> I thought it can but can't remember why now. OK, nm then, thanks!
FWIW (I think there was confusion in earlier discussions) we do merge
net into net-next once a week. So we can always apply stuff to net,
and then depending patches to net-next within a week. Just for future
reference, this patch IIUC we just leave be.
next prev parent reply other threads:[~2024-11-06 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 8:46 [PATCH net-next v1 0/4] virtio_net: enable premapped mode by default Xuan Zhuo
2024-10-29 8:46 ` [PATCH net-next v1 1/4] virtio-net: fix overflow inside virtnet_rq_alloc Xuan Zhuo
2024-11-05 9:22 ` Jason Wang
2024-11-06 7:37 ` Michael S. Tsirkin
2024-10-29 8:46 ` [PATCH net-next v1 2/4] virtio_net: big mode skip the unmap check Xuan Zhuo
2024-10-29 8:46 ` [PATCH net-next v1 3/4] virtio_net: enable premapped mode for merge and small by default Xuan Zhuo
2024-10-29 8:46 ` [PATCH net-next v1 4/4] virtio_net: rx remove premapped failover code Xuan Zhuo
2024-11-05 9:23 ` Jason Wang
2024-11-05 2:46 ` [PATCH net-next v1 0/4] virtio_net: enable premapped mode by default Jakub Kicinski
2024-11-05 5:07 ` Jason Wang
2024-11-06 7:38 ` Michael S. Tsirkin
2024-11-06 8:46 ` Xuan Zhuo
2024-11-06 9:16 ` Michael S. Tsirkin
2024-11-06 18:36 ` Jakub Kicinski [this message]
2024-11-05 11:00 ` 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=20241106103638.5844fe15@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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).