From: SeokYeon Hwang <syeon.hwang@samsung.com>
To: 'Markus Armbruster' <armbru@redhat.com>
Cc: 'Paolo Bonzini' <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "'Michael S. Tsirkin'" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pci: fixed mismatch of error-handling between pci_qdev_init() and qdev
Date: Mon, 10 Nov 2014 17:24:23 +0900 [thread overview]
Message-ID: <001a01cffcbf$bbc27470$33475d50$@samsung.com> (raw)
In-Reply-To: <87h9ybfo8p.fsf@blackfin.pond.sub.org>
> -----Original Message-----
> From: Markus Armbruster [mailto:armbru@redhat.com]
> Sent: Friday, November 07, 2014 4:45 PM
> To: SeokYeon Hwang
> Cc: 'Michael S. Tsirkin'; 'Paolo Bonzini'; qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] [PATCH] pci: fixed mismatch of error-handling
> between pci_qdev_init() and qdev
>
> SeokYeon Hwang <syeon.hwang@samsung.com> writes:
>
> [...]
> > But if 2.2 comes with all "realized" devices, if there is no "init"
> > devices, then this patch isn't needed.
>
> No PCI devices will be converted to realize in 2.2. We'll start the
> conversion early in the 2.3 development cycle. Whether we can finish it
> in the same cycle is uncertain.
Then...
I think 'pci_qdev_init()' should be fixed because it contains obviously
wrong logic.
I didn't understand why this problem should be ignored now for reasons of it
will be removed in the far future.
(or because all devices that use this function didn't return positive value
as error now.)
It will be corrected by
1. return '-1' instead of 'rc'.
2. check 'rc < 0' instead of 'rc != 0'. (if we can guarantee no pci device
returns positive value as error.)
What do you think about it ??
If I didn't understand the context of this thread, please let me know.
Thank you very much.
next prev parent reply other threads:[~2014-11-10 8:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 10:11 [Qemu-devel] [PATCH] pci: fixed mismatch of error-handling between pci_qdev_init() and qdev SeokYeon Hwang
2014-11-05 10:59 ` Paolo Bonzini
2014-11-05 12:46 ` Michael S. Tsirkin
2014-11-05 13:16 ` Markus Armbruster
2014-11-05 13:18 ` Paolo Bonzini
2014-11-05 13:28 ` Michael S. Tsirkin
2014-11-05 14:55 ` Paolo Bonzini
2014-11-06 2:26 ` SeokYeon Hwang
2014-11-06 9:20 ` Markus Armbruster
2014-11-06 9:26 ` Michael S. Tsirkin
2014-11-06 9:41 ` SeokYeon Hwang
2014-11-06 9:23 ` Michael S. Tsirkin
2014-11-07 4:17 ` SeokYeon Hwang
2014-11-07 7:45 ` Markus Armbruster
2014-11-10 8:24 ` SeokYeon Hwang [this message]
2014-11-10 8:50 ` Markus Armbruster
2014-11-05 13:28 ` SeokYeon Hwang
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='001a01cffcbf$bbc27470$33475d50$@samsung.com' \
--to=syeon.hwang@samsung.com \
--cc=armbru@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.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.