From: Paolo Bonzini <pbonzini@redhat.com>
To: "Hervé Poussineau" <hpoussin@reactos.org>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] esp: add missing const on TypeInfo structures
Date: Thu, 02 Aug 2012 17:54:55 +0200 [thread overview]
Message-ID: <501AA2CF.8070907@redhat.com> (raw)
In-Reply-To: <1343896830-3503-2-git-send-email-hpoussin@reactos.org>
Il 02/08/2012 10:40, Hervé Poussineau ha scritto:
>
> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
> ---
> hw/esp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/esp.c b/hw/esp.c
> index c6422ad..4b00889 100644
> --- a/hw/esp.c
> +++ b/hw/esp.c
> @@ -816,7 +816,7 @@ static void sysbus_esp_class_init(ObjectClass *klass, void *data)
> dc->vmsd = &vmstate_sysbus_esp_scsi;
> }
>
> -static TypeInfo sysbus_esp_info = {
> +static const TypeInfo sysbus_esp_info = {
> .name = "esp",
> .parent = TYPE_SYS_BUS_DEVICE,
> .instance_size = sizeof(SysBusESPState),
> @@ -1178,7 +1178,7 @@ static void esp_pci_class_init(ObjectClass *klass, void *data)
> dc->vmsd = &vmstate_esp_pci_scsi;
> }
>
> -static TypeInfo esp_pci_info = {
> +static const TypeInfo esp_pci_info = {
> .name = "am53c974",
> .parent = TYPE_PCI_DEVICE,
> .instance_size = sizeof(PCIESPState),
>
Applied to scsi-next branch.
Paolo
next prev parent reply other threads:[~2012-08-02 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 8:40 [Qemu-devel] [PATCH 1/2] qom: add missing 'const' in documentation sample Hervé Poussineau
2012-08-02 8:40 ` [Qemu-devel] [PATCH 2/2] esp: add missing const on TypeInfo structures Hervé Poussineau
2012-08-02 15:23 ` Andreas Färber
2012-08-02 15:54 ` Paolo Bonzini [this message]
2012-08-02 15:22 ` [Qemu-devel] [PATCH 1/2] qom: add missing 'const' in documentation sample Andreas Färber
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=501AA2CF.8070907@redhat.com \
--to=pbonzini@redhat.com \
--cc=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).