[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPv0NP7gms2FMOaysnphYSK=4qgo3GVKPd7pUMxsPS1C6bTj4g@mail.gmail.com>
Date: Thu, 13 Apr 2023 10:45:10 +0300
From: Viktor Prutyanov <viktor@...nix.com>
To: Alvaro Karsz <alvaro.karsz@...id-run.com>
Cc: "Michael S. Tsirkin" <mst@...hat.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
On Thu, Apr 13, 2023 at 10:40 AM Alvaro Karsz
<alvaro.karsz@...id-run.com> wrote:
>
> > 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.
Thank you!
Powered by blists - more mailing lists