[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR04MB4723AB600C87D77AB486D035D4989@AM0PR04MB4723.eurprd04.prod.outlook.com>
Date: Thu, 13 Apr 2023 07:40:11 +0000
From: Alvaro Karsz <alvaro.karsz@...id-run.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
CC: Viktor Prutyanov <viktor@...nix.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"cohuck@...hat.com" <cohuck@...hat.com>,
"pasic@...ux.ibm.com" <pasic@...ux.ibm.com>,
"farman@...ux.ibm.com" <farman@...ux.ibm.com>,
"linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"yan@...nix.com" <yan@...nix.com>
Subject: Re: [PATCH v6] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support
> Hmm. So it seems we need to first apply yours then this patch,
> is that right? Or the other way around? What is the right way to make it not break bisect?
> Do you mind including this patch with yours in a patchset
> in the correct order?
Ok, I'll create a patchset.
Thanks,
Powered by blists - more mailing lists