qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <xadimgnik@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>
Cc: Anthony PERARD <anthony@xenproject.org>,
	Richard Henderson <richard.henderson@linaro.org>,
	xen-devel@lists.xenproject.org,
	Stefano Stabellini <sstabellini@kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Eduardo Habkost <eduardo@habkost.net>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v2 7/7] hw/xen: Register framebuffer backend via xen_backend_init()
Date: Fri, 31 May 2024 10:59:18 +0100	[thread overview]
Message-ID: <0fe5773f-1524-4a9d-bdd8-606b18b4ced4@xen.org> (raw)
In-Reply-To: <20240510104908.76908-8-philmd@linaro.org>

On 10/05/2024 11:49, Philippe Mathieu-Daudé wrote:
> Align the framebuffer backend with the other legacy ones,
> register it via xen_backend_init() when '-vga xenfb' is
> used. It is safe because MODULE_INIT_XEN_BACKEND is called
> in xen_bus_realize(), long after CLI processing initialized
> the vga_interface_type variable.
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
>   include/hw/xen/xen-legacy-backend.h | 3 ---
>   hw/display/xenfb.c                  | 9 +++++++--
>   hw/xenpv/xen_machine_pv.c           | 2 --
>   3 files changed, 7 insertions(+), 7 deletions(-)
> 

Reviewed-by: Paul Durrant <paul@xen.org>



  reply	other threads:[~2024-05-31  9:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10 10:49 [PATCH v2 0/7] hw/xen: Simplify legacy backends handling Philippe Mathieu-Daudé
2024-05-10 10:49 ` [PATCH v2 1/7] hw/xen: Remove declarations left over in 'xen-legacy-backend.h' Philippe Mathieu-Daudé
2024-05-31  9:08   ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 2/7] hw/xen: Constify XenLegacyDevice::XenDevOps Philippe Mathieu-Daudé
2024-05-31  9:09   ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 3/7] hw/xen: Constify xenstore_be::XenDevOps Philippe Mathieu-Daudé
2024-05-31  9:10   ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 4/7] hw/xen: Make XenDevOps structures const Philippe Mathieu-Daudé
2024-05-31  9:52   ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 5/7] hw/xen: initialize legacy backends from xen_bus_init() Philippe Mathieu-Daudé
2024-05-31  9:56   ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 6/7] hw/xen: register legacy backends via xen_backend_init Philippe Mathieu-Daudé
2024-05-10 10:52   ` Philippe Mathieu-Daudé
2024-05-31  9:57   ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 7/7] hw/xen: Register framebuffer backend via xen_backend_init() Philippe Mathieu-Daudé
2024-05-31  9:59   ` Paul Durrant [this message]
2024-05-29  4:51 ` [PATCH v2 0/7] hw/xen: Simplify legacy backends handling Philippe Mathieu-Daudé
2024-06-03 11:48 ` Philippe Mathieu-Daudé

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=0fe5773f-1524-4a9d-bdd8-606b18b4ced4@xen.org \
    --to=xadimgnik@gmail.com \
    --cc=anthony@xenproject.org \
    --cc=eduardo@habkost.net \
    --cc=kraxel@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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).