From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/7] serial: add serial_chr_nonnull() to use the null backend when none provided
Date: Thu, 31 Aug 2017 17:23:55 +0200 [thread overview]
Message-ID: <5c9b4445-4870-a99f-058b-6de82959b302@redhat.com> (raw)
In-Reply-To: <800abf63-db3f-78c7-0580-8d86479fdf5a@amsat.org>
On 31.08.2017 17:20, Philippe Mathieu-Daudé wrote:
> On 08/31/2017 02:19 AM, Thomas Huth wrote:
>> On 31.08.2017 05:53, Philippe Mathieu-Daudé wrote:
> [...]>> +Chardev *serial_chr_nonnull(Chardev *chr)
>>> +{
>>> + static int serial_id;
>>> + char *label;
>>> +
>>> + label = g_strdup_printf("discarding-serial%d", serial_id++);
>>> + chr = qemu_chr_new(label, "null");
>>
>> That looks wrong - you're ignoring the input parameter and always open
>> the "null" device? Shouldn't there be a "if (chr) return chr;" in front
>> of this?
>
> You right. I had this correct in my first patch when this code was
> embedded, I then failed at extracting as another function :/
>
>>
>>> + assert(chr);
>>> + g_free(label);
>>> +
>>> + return chr;
>>> +}
>>
>> Thomas
>>
>> PS: I think you should also merge the two patches together, they are
>> small enough.
>
> Ok.
Well, I wrote that comment about merging the two patches together when I
was thinking that your series consists of only two patches (since I've
only been CC:-ed on the first two patches). So please simply ignore that
suggestion :-)
Thomas
next prev parent reply other threads:[~2017-08-31 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 3:52 [Qemu-devel] [PATCH 0/7] serial: add serial_chr_nonnull() Philippe Mathieu-Daudé
2017-08-31 3:53 ` [Qemu-devel] [PATCH 1/7] serial: add serial_chr_nonnull() to use the null backend when none provided Philippe Mathieu-Daudé
2017-08-31 5:19 ` Thomas Huth
2017-08-31 9:36 ` Marc-André Lureau
2017-08-31 9:43 ` Thomas Huth
2017-08-31 15:24 ` Philippe Mathieu-Daudé
2017-09-01 9:12 ` Markus Armbruster
2017-08-31 15:20 ` Philippe Mathieu-Daudé
2017-08-31 15:23 ` Thomas Huth [this message]
2017-08-31 10:28 ` Peter Maydell
2017-08-31 15:17 ` Philippe Mathieu-Daudé
2017-08-31 3:53 ` [Qemu-devel] [PATCH 2/7] serial: use serial_chr_nonnull() in serial_mm_init() Philippe Mathieu-Daudé
2017-08-31 3:53 ` [Qemu-devel] [PATCH 3/7] hw/arm/fsl_imx*: use serial_chr_nonnull() Philippe Mathieu-Daudé
2017-08-31 3:53 ` [Qemu-devel] [PATCH 4/7] hw/mips/malta: " Philippe Mathieu-Daudé
2017-08-31 3:53 ` [Qemu-devel] [PATCH 5/7] hw/char/exynos4210_uart: " Philippe Mathieu-Daudé
2017-08-31 3:53 ` [Qemu-devel] [PATCH 6/7] hw/char/omap_uart: serial_mm_init() already check for null chr Philippe Mathieu-Daudé
2017-08-31 3:53 ` [Qemu-devel] [PATCH 7/7] hw/xtensa: " Philippe Mathieu-Daudé
2017-09-05 14:56 ` [Qemu-devel] [PATCH 0/7] serial: add serial_chr_nonnull() Peter Maydell
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=5c9b4445-4870-a99f-058b-6de82959b302@redhat.com \
--to=thuth@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).