From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-ppc <qemu-ppc@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 0/4] cuda/mos6522 migration fixes
Date: Thu, 7 Jun 2018 21:17:18 +0100 [thread overview]
Message-ID: <CAFEAcA_qc-x0rnDRyJaoiZyL=G2BU6HoiiKbzV=_phRMwHo4zA@mail.gmail.com> (raw)
In-Reply-To: <8484d1a4-b9e4-3d69-090c-22c230878566@amsat.org>
On 7 June 2018 at 20:18, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> You forgot patch 5 "vmstate: Remove VMSTATE_TIMER_PTR_TEST" :)
It's a generic macro that might have utility in future,
and it fits into a slot in the matrix of possible VMSTATE
macros, so I wouldn't bother. (It's kind of irritating that we
have an almost but not quite orthogonal set of VMSTATE
macros.)
thanks
-- PMM
next prev parent reply other threads:[~2018-06-07 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 17:17 [Qemu-devel] [PATCH 0/4] cuda/mos6522 migration fixes Mark Cave-Ayland
2018-06-07 17:17 ` [Qemu-devel] [PATCH 1/4] mos6522: fix vmstate_mos6522_timer version in vmstate_mos6522 Mark Cave-Ayland
2018-06-07 17:17 ` [Qemu-devel] [PATCH 2/4] cuda: embed mos6522_cuda device directly rather than using QOM object link Mark Cave-Ayland
2018-06-08 2:13 ` David Gibson
2018-06-07 17:17 ` [Qemu-devel] [PATCH 3/4] mos6522: move timer frequency initialisation to mos6522_reset Mark Cave-Ayland
2018-06-07 17:17 ` [Qemu-devel] [PATCH 4/4] mos6522: convert VMSTATE_TIMER_PTR_TEST to VMSTATE_TIMER_PTR Mark Cave-Ayland
2018-06-07 19:28 ` Peter Maydell
2018-06-07 19:18 ` [Qemu-devel] [PATCH 0/4] cuda/mos6522 migration fixes Philippe Mathieu-Daudé
2018-06-07 20:17 ` Peter Maydell [this message]
2018-06-07 21:10 ` Philippe Mathieu-Daudé
2018-06-08 2:11 ` David Gibson
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='CAFEAcA_qc-x0rnDRyJaoiZyL=G2BU6HoiiKbzV=_phRMwHo4zA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=f4bug@amsat.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).