From: Keqian Zhu <zhukeqian1@huawei.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Rob Herring <robh@kernel.org>,
qemu-trivial@nongnu.org, qemu-arm@nongnu.org,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH 0/3] hw: Constify VMStateDescription
Date: Mon, 15 Mar 2021 17:05:43 +0800 [thread overview]
Message-ID: <bd47e690-dab6-e8db-2d8c-aa729c41abad@huawei.com> (raw)
In-Reply-To: <20210313171150.2122409-1-f4bug@amsat.org>
Hi Philippe,
It seems that vmstate_ecc_state and vmstate_x86_cpu can also be constified.
Found by <git grep "VMStateDescription" | grep -v "const">.
Thanks,
Keqian
On 2021/3/14 1:11, Philippe Mathieu-Daudé wrote:
> VMStateDescription isn't supposed to be modified.
>
>
>
> Philippe Mathieu-Daudé (3):
>
> hw/arm: Constify VMStateDescription
>
> hw/display/qxl: Constify VMStateDescription
>
> hw/usb: Constify VMStateDescription
>
>
>
> hw/arm/highbank.c | 2 +-
>
> hw/arm/pxa2xx_pic.c | 2 +-
>
> hw/arm/spitz.c | 4 ++--
>
> hw/arm/strongarm.c | 2 +-
>
> hw/arm/z2.c | 4 ++--
>
> hw/display/qxl.c | 8 ++++----
>
> hw/dma/pxa2xx_dma.c | 4 ++--
>
> hw/misc/mst_fpga.c | 2 +-
>
> hw/usb/ccid-card-passthru.c | 2 +-
>
> hw/usb/dev-smartcard-reader.c | 8 ++++----
>
> 10 files changed, 19 insertions(+), 19 deletions(-)
>
>
>
next prev parent reply other threads:[~2021-03-15 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 17:11 [PATCH 0/3] hw: Constify VMStateDescription Philippe Mathieu-Daudé
2021-03-13 17:11 ` [PATCH 1/3] hw/arm: " Philippe Mathieu-Daudé
2021-04-30 16:16 ` Laurent Vivier
2021-03-13 17:11 ` [PATCH 2/3] hw/display/qxl: " Philippe Mathieu-Daudé
2021-04-30 16:17 ` Laurent Vivier
2021-03-13 17:11 ` [PATCH 3/3] hw/usb: " Philippe Mathieu-Daudé
2021-04-30 16:19 ` Laurent Vivier
2021-03-13 17:24 ` [PATCH 0/3] hw: " Richard Henderson
2021-03-15 9:05 ` Keqian Zhu [this message]
2021-04-08 13:22 ` Philippe Mathieu-Daudé
2021-04-08 13:46 ` Keqian Zhu
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=bd47e690-dab6-e8db-2d8c-aa729c41abad@huawei.com \
--to=zhukeqian1@huawei.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=robh@kernel.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).