From: David Woodhouse <dwmw2@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Peter Hilber <peter.hilber@opensynergy.com>,
"Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>
Subject: Re: [PATCH v2] hw/acpi: Add vmclock device
Date: Thu, 01 Aug 2024 09:49:06 +0100 [thread overview]
Message-ID: <a432792506935843c0d5c4323ea70ef8df1dbefd.camel@infradead.org> (raw)
In-Reply-To: <20240731171843-mutt-send-email-mst@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
On Wed, 2024-07-31 at 17:19 -0400, Michael S. Tsirkin wrote:
>
> > Perfect. So as and when the header is in its final form in Linux,
> > it can be part of the automated import and we'll use that version.
> > At that point we can drop the one that's sitting alongside the
> > device itself in hw/acpi/.
>
> Yes. Maybe add a comment in the temporary header.
I pondered that, but kind of preferred to have it byte-identical.
Admittedly I'm not *planning* to have to change it any more but it's
been useful so far that I can just *copy* the file between the Linux
and Linux-backport and QEMU repositories.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2024-08-01 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 16:33 [PATCH v2] hw/acpi: Add vmclock device David Woodhouse
2024-07-30 17:53 ` Michael S. Tsirkin
2024-07-30 19:04 ` David Woodhouse
2024-07-30 20:45 ` Michael S. Tsirkin
2024-07-31 0:23 ` David Woodhouse
2024-07-31 21:19 ` Michael S. Tsirkin
2024-08-01 8:49 ` David Woodhouse [this message]
2024-08-01 9:48 ` Michael S. Tsirkin
2024-08-01 10:00 ` David Woodhouse
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=a432792506935843c0d5c4323ea70ef8df1dbefd.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=abuehaze@amazon.com \
--cc=anisinha@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.hilber@opensynergy.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).