All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
	Thomas Huth <thuth@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Alexander Graf <agraf@suse.de>,
	borntraeger@de.ibm.com, Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1] target/s390x: change CPU type name to "s390x-cpu"
Date: Wed, 25 Oct 2017 11:52:45 +0200	[thread overview]
Message-ID: <20171025115245.7702c8aa.cohuck@redhat.com> (raw)
In-Reply-To: <20171020115803.14093-1-david@redhat.com>

On Fri, 20 Oct 2017 13:58:03 +0200
David Hildenbrand <david@redhat.com> wrote:

> For now, e.g. host-s390-cpu wasn't exposed to the user. cpu-add, -cpu
> and the CPU model qmp interfaces didn't care about the actual type,
> as that information was hidden.
> 
> This changed with CPU hotplug via device_add. Now the type is visible to
> the user. Before we get that supported in a stable version, this is our
> last chance to change it.
> 
> So change it form "s390-cpu" to "s390x-cpu", to match the architecture
> name. Example names are then e.g. z14-s390x-cpu or qemu-s390x-cpu.
> 
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>  qapi-schema.json          | 4 ++--
>  target/s390x/cpu-qom.h    | 2 +-
>  target/s390x/cpu_models.c | 4 ++--
>  3 files changed, 5 insertions(+), 5 deletions(-)

Acked-by: Cornelia Huck <cohuck@redhat.com>

  parent reply	other threads:[~2017-10-25  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 11:58 [Qemu-devel] [PATCH v1] target/s390x: change CPU type name to "s390x-cpu" David Hildenbrand
2017-10-20 12:44 ` Thomas Huth
2017-10-20 15:23   ` David Hildenbrand
2017-10-20 15:26 ` Eric Blake
2017-10-25  9:39   ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2017-10-25  9:52 ` Cornelia Huck [this message]
2017-10-25 10:12 ` [Qemu-devel] " Christian Borntraeger

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=20171025115245.7702c8aa.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    /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.