From: "Cédric Le Goater" <clg@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
qemu-devel@nongnu.org, lersek@redhat.com
Subject: Re: [PATCH v5 0/3] ramfb: migration support
Date: Thu, 12 Oct 2023 12:11:53 +0200 [thread overview]
Message-ID: <a99d25e9-dfa5-0699-5b46-aa5ab23f0b56@redhat.com> (raw)
In-Reply-To: <foqw7o42pm7fys42zscstnfln77sof237j7slqcbupyximekba@p7uj37bce2nh>
On 10/12/23 11:18, Gerd Hoffmann wrote:
> On Wed, Oct 11, 2023 at 07:09:19PM +0200, Cédric Le Goater wrote:
>> On 10/10/23 15:46, Marc-André Lureau wrote:
>>> Hi
>>>
>>> On Tue, Oct 10, 2023 at 4:49 PM Cédric Le Goater <clg@redhat.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> On 10/9/23 08:32, marcandre.lureau@redhat.com wrote:
>>>>> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>>>>>
>>>>> Hi,
>>>>>
>>>>> Implement RAMFB migration, and add properties to enable it only on >= 8.2
>>>>> machines, + a few related cleanups.
>>>>
>>>> Should this series go in vfio-next ?
>>>>
>>>
>>> That's a good option for me.
>>
>> Gerd, fine with you ?
>
> Yes.
>
> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Thanks,
Applied to vfio-next.
C.
prev parent reply other threads:[~2023-10-12 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 6:32 [PATCH v5 0/3] ramfb: migration support marcandre.lureau
2023-10-09 6:32 ` [PATCH v5 1/3] ramfb: add " marcandre.lureau
2023-10-09 6:32 ` [PATCH v5 2/3] ramfb-standalone: " marcandre.lureau
2023-10-09 6:32 ` [PATCH v5 3/3] hw/vfio: add ramfb " marcandre.lureau
2023-10-09 10:19 ` Laszlo Ersek
2023-10-10 7:03 ` Cédric Le Goater
2023-10-10 7:08 ` Marc-André Lureau
2023-10-10 12:48 ` [PATCH v5 0/3] ramfb: " Cédric Le Goater
2023-10-10 13:46 ` Marc-André Lureau
2023-10-11 17:09 ` Cédric Le Goater
2023-10-12 9:18 ` Gerd Hoffmann
2023-10-12 10:11 ` Cédric Le Goater [this message]
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=a99d25e9-dfa5-0699-5b46-aa5ab23f0b56@redhat.com \
--to=clg@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).