All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jia Liu <proljc@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name
Date: Mon, 22 Jul 2013 12:37:46 +0200	[thread overview]
Message-ID: <51ED0B7A.2010205@suse.de> (raw)
In-Reply-To: <CAFEAcA-75cp9GtZbWPCM=sDW+dHmu7pRNhEUmQZS=5ZnVqTk7Q@mail.gmail.com>

Am 22.07.2013 11:43, schrieb Peter Maydell:
> On 22 July 2013 10:42, Jia Liu <proljc@gmail.com> wrote:
>> Hi Andreas and Peter,
>>
>> On Mon, Jul 22, 2013 at 5:29 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> This looks a bit odd. The commit message suggests it's an
>>> attempt to fix the bug that was fixed by commit 071b3364e --
>>> is it really needed? Andreas?
>>
>> commit 071b3364e fix the typename only, but this one make "-cpu any"
>> "-cpu or1200" "-cpu any-or32-cpu" "-cpu or1200-or32-cpu" working fine.
> 
> The last two of these would be wrong: -cpu should only
> accept CPU names, ie "any" or "or1200".

Peter, the story is that due to an oversight on my part, it was possible
to use -cpu or1200-or32-cpu only for some weeks or months. This has been
fixed so that only -cpu or1200 works.

It is up to Jia whether he sees a need to have both work or whether -cpu
or1200 would be sufficient. In any case, I was not CC'ed on this series,
so I only came across one patch by accident during a search for
something else. ;)

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2013-07-22 10:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  8:56 [Qemu-devel] [PATCH v3 0/4] target-openrisc hw/openrisc: Some OpenRISC fix Jia Liu
2013-07-22  8:56 ` [Qemu-devel] [PATCH v3 1/4] hw/openrisc: Indent typo Jia Liu
2013-07-22  9:21   ` Peter Maydell
2013-07-22  8:56 ` [Qemu-devel] [PATCH v3 2/4] hw/openrisc: Use stderr output instead of qemu_log Jia Liu
2013-07-22  9:21   ` Peter Maydell
2013-07-22  8:56 ` [Qemu-devel] [PATCH v3 3/4] target-openrisc: Free typename Jia Liu
2013-07-22  9:37   ` Jia Liu
2013-07-22  9:41     ` Peter Maydell
2013-07-22  9:43       ` Jia Liu
2013-07-22  8:56 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Jia Liu
2013-07-22  9:29   ` Peter Maydell
2013-07-22  9:42     ` Jia Liu
2013-07-22  9:43       ` Peter Maydell
2013-07-22  9:54         ` Jia Liu
2013-07-22 10:12         ` Jia Liu
2013-07-22 10:37         ` Andreas Färber [this message]
2013-07-22 10:40           ` Peter Maydell
2013-07-22 11:17             ` Andreas Färber
2013-07-22 11:34               ` Peter Maydell
2013-07-22 12:26                 ` [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name) Andreas Färber
2013-07-22 12:33                 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Andreas Färber
2013-07-22 15:25                   ` Anthony Liguori
2013-07-22 15:38                     ` Peter Maydell
2013-07-22 16:29                       ` [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name) Andreas Färber
2013-07-22 17:39                       ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Anthony Liguori

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=51ED0B7A.2010205@suse.de \
    --to=afaerber@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=proljc@gmail.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.