From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: marcel@redhat.com, qemu-devel@nongnu.org
Cc: mst@redhat.com, qemu-ppc@nongnu.org, agraf@suse.de, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 2/2] change type of pci_bridge_initfn() to void
Date: Fri, 15 Jan 2016 09:59:17 +0800 [thread overview]
Message-ID: <56985275.3030600@cn.fujitsu.com> (raw)
In-Reply-To: <5697C1D7.2050309@gmail.com>
On 01/14/2016 11:42 PM, Marcel Apfelbaum wrote:
> On 01/14/2016 02:23 PM, Cao jin wrote:
>> diff --git a/hw/pci-host/apb.c b/hw/pci-host/apb.c
>> index 599768e..e9117b9 100644
>> --- a/hw/pci-host/apb.c
>> +++ b/hw/pci-host/apb.c
>> @@ -636,10 +636,7 @@ static int apb_pci_bridge_initfn(PCIDevice *dev)
>> {
>> int rc;
>>
>> - rc = pci_bridge_initfn(dev, TYPE_PCI_BUS);
>> - if (rc < 0) {
>> - return rc;
>> - }
>> + pci_bridge_initfn(dev, TYPE_PCI_BUS);
>>
>
> Hi,
>
> It seems you don't need the rc variable here anymore, right?
>
> This should break the build (unused local variable),
Indeed...
> I suggest running configure with no params to check all the architectures,
> (I am also running make check while at it, just to be sure)
>
Thanks for the suggestion, really should that when touched so many device.
> Thanks,
> Marcel
>
> .
>
--
Yours Sincerely,
Cao jin
next prev parent reply other threads:[~2016-01-15 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 12:23 [Qemu-devel] [PATCH v3 0/2] change type of pci_bridge_initfn() Cao jin
2016-01-14 12:23 ` [Qemu-devel] [PATCH v3 1/2] dec: convert to realize() Cao jin
2016-01-14 14:27 ` Marcel Apfelbaum
2016-01-14 12:23 ` [Qemu-devel] [PATCH v3 2/2] change type of pci_bridge_initfn() to void Cao jin
2016-01-14 15:42 ` Marcel Apfelbaum
2016-01-15 1:59 ` Cao jin [this message]
2016-01-14 12:31 ` [Qemu-devel] [PATCH v3 0/2] change type of pci_bridge_initfn() Cao jin
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=56985275.3030600@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).