From: Junnan Wu <junnan01.wu@samsung.com>
To: sgarzare@redhat.com
Cc: davem@davemloft.net, edumazet@google.com, eperezma@redhat.com,
horms@kernel.org, jasowang@redhat.com, junnan01.wu@samsung.com,
kuba@kernel.org, kvm@vger.kernel.org, lei19.wang@samsung.com,
linux-kernel@vger.kernel.org, mst@redhat.com,
netdev@vger.kernel.org, pabeni@redhat.com, q1.huang@samsung.com,
stefanha@redhat.com, virtualization@lists.linux.dev,
xuanzhuo@linux.alibaba.com, ying01.gao@samsung.com,
ying123.xu@samsung.com
Subject: Re: Re: [Patch net 1/2] vsock/virtio: initialize rx_buf_nr and rx_buf_max_nr when resuming
Date: Fri, 14 Feb 2025 09:02:47 +0800 [thread overview]
Message-ID: <20250214010247.4071303-1-junnan01.wu@samsung.com> (raw)
In-Reply-To: <CAGxU2F7PKH34N7Jd5d=STCAybJi-DDTB-XGiXSAS9BBvGVN4GA@mail.gmail.com>
On Thu, 13 Feb 2025 at 15:47, Stefano Garzarella <sgarzare@redhat.com> wrote:
>I forgot to mention that IMHO it's better to split this series.
>This first patch (this one) seems ready, without controversy, and it's
>a real fix, so for me v3 should be a version ready to be merged.
>
>While the other patch is more controversial and especially not a fix
>but more of a new feature, so I don't think it makes sense to continue
>to have these two patches in a single series.
>
>Thanks,
>Stefano
Well, I agree with you that these two patches should be splited.
And I will send v3 version of the first patch individually.
And according to our discussion, the second one can be ignored, until
we find a suitable way to deal the scenario I metionded.
Thanks,
Junnan
next prev parent reply other threads:[~2025-02-14 1:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250211071930epcas5p2dbb3a4171fbe04574c0fa7b3a6f1a0c2@epcas5p2.samsung.com>
2025-02-11 7:19 ` [Patch net 0/2] vsock suspend/resume fix Junnan Wu
2025-02-11 7:19 ` [Patch net 1/2] vsock/virtio: initialize rx_buf_nr and rx_buf_max_nr when resuming Junnan Wu
2025-02-11 8:57 ` Stefano Garzarella
2025-02-13 1:28 ` Junnan Wu
2025-02-13 9:25 ` Stefano Garzarella
2025-02-13 14:47 ` Stefano Garzarella
2025-02-14 1:02 ` Junnan Wu [this message]
2025-02-14 1:22 ` [Patch net v3] vsock/virtio: fix variables initialization during resuming Junnan Wu
2025-02-14 9:13 ` Luigi Leonardi
2025-02-14 12:17 ` Michael S. Tsirkin
2025-02-14 13:34 ` Stefano Garzarella
2025-02-15 4:00 ` patchwork-bot+netdevbpf
2025-02-11 7:19 ` [Patch net 2/2] vsock/virtio: Don't reset the created SOCKET during suspend to ram Junnan Wu
2025-02-11 8:49 ` Stefano Garzarella
2025-02-15 14:26 ` Markus Elfring
2025-02-11 8:54 ` [Patch net 0/2] vsock suspend/resume fix Stefano Garzarella
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=20250214010247.4071303-1-junnan01.wu@samsung.com \
--to=junnan01.wu@samsung.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lei19.wang@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=q1.huang@samsung.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
--cc=ying01.gao@samsung.com \
--cc=ying123.xu@samsung.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).