From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] of apci_1_compatible in CPUHotplugFeatures
Date: Tue, 22 Jan 2019 22:00:20 -0500 [thread overview]
Message-ID: <20190122215941-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190122200740.GC2241@work-vm>
On Tue, Jan 22, 2019 at 08:07:41PM +0000, Dr. David Alan Gilbert wrote:
> Hi,
> I noticed that the acpi_1_compatible flag was misspelt as
> apci_1_compatible
>
> so have a trivial patch to fix that, but looking at it - are
> thre any cases where a[cp]i_1_compatible can possibly be false?
>
> Dave
legacy_cpu_hotplug so machine 2.6 and older - no?
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-01-23 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 20:07 [Qemu-devel] of apci_1_compatible in CPUHotplugFeatures Dr. David Alan Gilbert
2019-01-23 3:00 ` Michael S. Tsirkin [this message]
2019-01-23 18:28 ` Dr. David Alan Gilbert
2019-01-25 8:26 ` Igor Mammedov
2019-01-25 9:41 ` Dr. David Alan Gilbert
2019-01-25 19:49 ` Michael S. Tsirkin
2019-01-28 10:41 ` Igor Mammedov
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=20190122215941-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.