From: "Andreas Färber" <afaerber@suse.de>
To: Jia Liu <proljc@gmail.com>, Dongxue Zhang <elta.era@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target-openrisc: Add typename for CPU models.
Date: Sun, 07 Jul 2013 18:08:31 +0200 [thread overview]
Message-ID: <51D9927F.1040402@suse.de> (raw)
In-Reply-To: <CAJBMM-tezyfL0VXapusexncW-ojXNMzWZmxZk5sidEeipU4GEw@mail.gmail.com>
Hi,
Am 02.07.2013 14:30, schrieb Jia Liu:
> On Tue, Jul 2, 2013 at 6:18 PM, Andreas Färber <afaerber@suse.de
> <mailto:afaerber@suse.de>> wrote:
>> Am 02.07.2013 11:29, schrieb Jia Liu:
>> > On Tue, Jul 2, 2013 at 5:11 PM, Dongxue Zhang <elta.era@gmail.com
> <mailto:elta.era@gmail.com>
>> > <mailto:elta.era@gmail.com <mailto:elta.era@gmail.com>>> wrote:
>> >>
>> >> Make target-openrisc running OK by add typename in
>> > openrisc_cpu_class_by_name().
>> >>
>> >> Signed-off-by: Dongxue Zhang <elta.era@gmail.com
> <mailto:elta.era@gmail.com>
>> > <mailto:elta.era@gmail.com <mailto:elta.era@gmail.com>>>
>> >> ---
>> >> target-openrisc/cpu.c | 4 +++-
>> >> 1 file changed, 3 insertions(+), 1 deletion(-)
>> >>
>> >> diff --git a/target-openrisc/cpu.c b/target-openrisc/cpu.c
>> >> index fd90d37..d38c28b 100644
>> >> --- a/target-openrisc/cpu.c
>> >> +++ b/target-openrisc/cpu.c
>> >> @@ -96,12 +96,14 @@ static void openrisc_cpu_initfn(Object *obj)
>> >> static ObjectClass *openrisc_cpu_class_by_name(const char *cpu_model)
>> >> {
>> >> ObjectClass *oc;
>> >> + char *typename;
>> >>
>> >> if (cpu_model == NULL) {
>> >> return NULL;
>> >> }
>> >>
>> >> - oc = object_class_by_name(cpu_model);
>> >> + typename = g_strdup_printf("%s-" TYPE_OPENRISC_CPU, cpu_model);
>> >> + oc = object_class_by_name(typename);
>> >> if (oc != NULL && (!object_class_dynamic_cast(oc,
>> > TYPE_OPENRISC_CPU) ||
>> >> object_class_is_abstract(oc))) {
>> >> return NULL;
>> >
>> > Thanks for your fix, it looks and test good to me.
>>
>> Sorry for the breakage. Do you want to add a
>> Reviewed-by/Tested-by/Acked-by? I'd queue it for you then.
Thanks, queued on qom-cpu (with extended commit message):
https://github.com/afaerber/qemu-cpu/commits/qom-cpu
CC'ing qemu-stable. I also note that my mistake made it possible to use
-cpu or1200-or32-cpu or -cpu any-or32-cpu instead of -cpu or1200 or -cpu
any, which this patch reverts. I believe that to be intentional.
Otherwise we can extend the patch to allow both.
> Thank you very much! May you please tell me how can I make a
> Reviewed-by/Tested-by/Acked-by? I don't know too much about it.
You can see how it's used on the list almost every day. ;)
Reviewed-by: Your Name <your@email> means that you have reviewed the
patch to be sensible, functionally correct and containing no style issues.
Tested-by should be obvious. Based on your email I've added that one for
now.
Acked-by is short for acknowledged and, depending on interpretation,
means either that the change/concept looks okay or that it has been
reviewed and compile-tested. Anthony prefers to get Reviewed-bys.
>> If you could upload a Linux test image somewhere that may help avoid
>> breakages in the future.
>
> I find some Linux test images at http://qemu-project.org/Testing . How
> can I upload one upon to there?
We can't. For one the Wiki has an upload file size limit, for another
hosting GPL'ed binaries requires to either host or supply on request the
corresponding source code (but IANAL).
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-07-07 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 9:11 [Qemu-devel] [PATCH] target-openrisc: Add typename for CPU models Dongxue Zhang
2013-07-02 9:29 ` Jia Liu
2013-07-02 10:18 ` Andreas Färber
2013-07-02 12:30 ` Jia Liu
2013-07-07 16:08 ` Andreas Färber [this message]
2013-07-08 2:06 ` Jia Liu
2013-07-05 23:48 ` Jia Liu
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=51D9927F.1040402@suse.de \
--to=afaerber@suse.de \
--cc=elta.era@gmail.com \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).