[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5a401aaa-b6cd-46d4-9fd8-96753599b440@web.de>
Date: Sat, 15 Feb 2025 15:26:15 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Junnan Wu <junnan01.wu@...sung.com>, Ying Gao <ying01.gao@...sung.com>,
kvm@...r.kernel.org, netdev@...r.kernel.org, virtualization@...ts.linux.dev,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Jason Wang <jasowang@...hat.com>,
"Michael S. Tsirkin" <mst@...hat.com>, Paolo Abeni <pabeni@...hat.com>,
Stefan Hajnoczi <stefanha@...hat.com>,
Stefano Garzarella <sgarzare@...hat.com>
Cc: LKML <linux-kernel@...r.kernel.org>, Eugenio Pérez
<eperezma@...hat.com>, Simon Horman <horms@...nel.org>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, lei19.wang@...sung.com,
q1.huang@...sung.com, ying123.xu@...sung.com
Subject: Re: [Patch net 2/2] vsock/virtio: Don't reset the created SOCKET
during suspend to ram
…
> and it will cause that socket can not be unusable after resume.
…
I find such a wording confusing.
Can the change description become clearer?
Regards,
Markus
Powered by blists - more mailing lists