From: Jakub Kicinski <kuba@kernel.org>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: virtualization@lists.linux-foundation.org,
Jason Wang <jasowang@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH vhost 0/2] virtio_net: fix for stuck when change ring size with dev down
Date: Fri, 12 Aug 2022 12:47:32 -0700 [thread overview]
Message-ID: <20220812124732.75023d98@kernel.org> (raw)
In-Reply-To: <1660267838.1945586-1-xuanzhuo@linux.alibaba.com>
On Fri, 12 Aug 2022 09:30:38 +0800 Xuan Zhuo wrote:
> Yes, the commits fixed by this patch are currently in Michael's vhost branch.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/log/?h=linux-next
>
> So I mean that by "vhost" here, not into the net/net-next branch. Or should I use
> a more accurate term next time?
The tagging seems good, perhaps add a note to the commit message next
time. Maybe a lore link to the series you are fixing up?
The virtio_net.c patches usually go via netdev AFAIU and we're lacking
the vhost context.
prev parent reply other threads:[~2022-08-12 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 8:02 [PATCH vhost 0/2] virtio_net: fix for stuck when change ring size with dev down Xuan Zhuo
2022-08-11 8:02 ` Xuan Zhuo
2022-08-11 8:02 ` [PATCH 1/2] virtio_net: fix for stuck when change rx " Xuan Zhuo
2022-08-11 8:02 ` Xuan Zhuo
2022-08-11 8:02 ` [PATCH 2/2] virtio_net: fix for stuck when change tx " Xuan Zhuo
2022-08-11 8:02 ` Xuan Zhuo
2022-08-11 8:11 ` [PATCH vhost 0/2] virtio_net: fix for stuck when change " Michael S. Tsirkin
2022-08-11 8:11 ` Michael S. Tsirkin
2022-08-11 8:12 ` Xuan Zhuo
2022-08-11 8:12 ` Xuan Zhuo
2022-08-11 17:37 ` Jakub Kicinski
2022-08-12 1:30 ` Xuan Zhuo
2022-08-12 1:30 ` Xuan Zhuo
2022-08-12 19:47 ` Jakub Kicinski [this message]
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=20220812124732.75023d98@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.