[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALeUXe7OGUUt+5hpiLcg=1vWsOWkSRLN3Lb-ncpXZZjsgZntjQ@mail.gmail.com>
Date: Fri, 11 Mar 2022 10:26:08 +0900
From: Jiyong Park <jiyong@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
Stefano Garzarella <sgarzare@...hat.com>,
Stefan Hajnoczi <stefanha@...hat.com>,
Jason Wang <jasowang@...hat.com>,
"David S. Miller" <davem@...emloft.net>, adelva@...gle.com,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] vsock: each transport cycles only on its own sockets
First of all, sorry for the stupid breakage I made in V2. I forgot to turn
CONFIG_VMWARE_VMCI_VSOCKETS on when I did the build by
myself. I turned it on later and fixed the build error in V3.
> Jiyong, would you mind collecting the tags from Stefano and Michael
> and reposting? I fixed our build bot, it should build test the patch
> - I can't re-run on an already ignored patch, sadly.
Jakub, please bear with me; Could you explain what you exactly want
me to do? I'm new to kernel development and don't know how changes
which Stefano and Machael maintain get tested and staged.
Powered by blists - more mailing lists