From: Don Slutz <don.slutz@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] target-i386: Report on error during cpu_x86_register().
Date: Sun, 02 Sep 2012 19:40:27 -0400 [thread overview]
Message-ID: <5043EE6B.70509@CloudSwitch.com> (raw)
In-Reply-To: <CAAu8pHsbxJrO+rRG8Hs8V9y65gm1RHJ0+UGWjxLapZatvVw5AA@mail.gmail.com>
Blue Swirl wrote:
> On Sat, Sep 1, 2012 at 8:47 PM, Don Slutz <Don@cloudswitch.com> wrote:
>
>> Send it to stderr before free of the details.
>>
>> Signed-off-by: Don Slutz <Don@CloudSwitch.com>
>> ---
>> target-i386/cpu.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
>> index 57c064f..5c0fef1 100644
>> --- a/target-i386/cpu.c
>> +++ b/target-i386/cpu.c
>> @@ -1352,6 +1352,7 @@ int cpu_x86_register(X86CPU *cpu, const char *cpu_model)
>> }
>> object_property_set_str(OBJECT(cpu), def->model_id, "model-id", &error);
>> if (error_is_set(&error)) {
>> + fprintf(stderr, "%s: %s\n", __FUNCTION__, error_get_pretty(error));
>>
>
> __func__ is preferred by checkpatch.pl and also GCC recommends using it:
> http://gcc.gnu.org/onlinedocs/gcc/Function-Names.html
>
>
>> error_free(error);
>> return -1;
>> }
>> --
>> 1.7.1
>>
>>
>>
Somehow I forgot to run checkpatch.pl on this. V2 soon.
-Don
WARNING: multiple messages have this Message-ID (diff)
From: Don Slutz <don.slutz@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-i386: Report on error during cpu_x86_register().
Date: Sun, 02 Sep 2012 19:40:27 -0400 [thread overview]
Message-ID: <5043EE6B.70509@CloudSwitch.com> (raw)
In-Reply-To: <CAAu8pHsbxJrO+rRG8Hs8V9y65gm1RHJ0+UGWjxLapZatvVw5AA@mail.gmail.com>
Blue Swirl wrote:
> On Sat, Sep 1, 2012 at 8:47 PM, Don Slutz <Don@cloudswitch.com> wrote:
>
>> Send it to stderr before free of the details.
>>
>> Signed-off-by: Don Slutz <Don@CloudSwitch.com>
>> ---
>> target-i386/cpu.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
>> index 57c064f..5c0fef1 100644
>> --- a/target-i386/cpu.c
>> +++ b/target-i386/cpu.c
>> @@ -1352,6 +1352,7 @@ int cpu_x86_register(X86CPU *cpu, const char *cpu_model)
>> }
>> object_property_set_str(OBJECT(cpu), def->model_id, "model-id", &error);
>> if (error_is_set(&error)) {
>> + fprintf(stderr, "%s: %s\n", __FUNCTION__, error_get_pretty(error));
>>
>
> __func__ is preferred by checkpatch.pl and also GCC recommends using it:
> http://gcc.gnu.org/onlinedocs/gcc/Function-Names.html
>
>
>> error_free(error);
>> return -1;
>> }
>> --
>> 1.7.1
>>
>>
>>
Somehow I forgot to run checkpatch.pl on this. V2 soon.
-Don
next prev parent reply other threads:[~2012-09-02 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 20:47 [Qemu-trivial] [PATCH] target-i386: Report on error during cpu_x86_register() Don Slutz
2012-09-01 20:47 ` [Qemu-devel] " Don Slutz
2012-09-02 10:54 ` [Qemu-trivial] " Blue Swirl
2012-09-02 10:54 ` Blue Swirl
2012-09-02 23:40 ` Don Slutz [this message]
2012-09-02 23:40 ` Don Slutz
2012-09-03 0:09 ` [Qemu-trivial] [PATCH v2] " Don Slutz
2012-09-03 0:09 ` [Qemu-devel] " Don Slutz
2012-09-11 14:13 ` [Qemu-trivial] " Don Slutz
2012-09-11 14:13 ` [Qemu-devel] " Don Slutz
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=5043EE6B.70509@CloudSwitch.com \
--to=don.slutz@gmail.com \
--cc=Don@CloudSwitch.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.