From: Yijing Wang <wangyijing@huawei.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rafael <rjw@sisk.pl>, Hanjun Guo <guohanjun@huawei.com>,
Jiang Liu <jiang.liu@huawei.com>
Subject: Re: [PATCH 1/3] PCI,acpiphp: use generic pci_hp_add_bridge()
Date: Tue, 16 Apr 2013 14:43:49 +0800 [thread overview]
Message-ID: <516CF325.40604@huawei.com> (raw)
In-Reply-To: <CAE9FiQUACgSPffKQrKvb3zbrm-pg3gxkWxahNFFHofkW33sHwA@mail.gmail.com>
> On Mon, Apr 15, 2013 at 6:49 PM, Yijing Wang <wangyijing@huawei.com> wrote:
>> Hi Yinghai,
>> Any comments about this patch? I searched the code history and found
>> you introduced pci_hp_add_bridge() function at commit a8e4b9c10. In your
>> patchset use pci_hp_add_bridge() for all pci hotplug drivers except acpiphp.
>> So I use pci_hp_add_bridge() in acpiphp instead of using pci_scan_bridge()
>> directly. I would appreciate if you can give some suggestions.
Hi Yinghai,
Thanks for your review and comments very much!
>
> There is one problem in your patch.
> max start value get change. before your patch max is the maximum value
> of bus all children...
> now it is change bus start value.
Thank you for reminding. Now I noticed this detail.(:
I will drop these pathes.
Thanks!
Yijing.
>
> looks like old code try to handle the case that we already some
> children on that bus.
>
> Last time i did not change it, because i think it only is ready after
> busn_res alloc patchset
> is merged.
>
> in pci-mini summit of last year, Bjorn asked Linus about that
> patchset, and Linus said it is
> risky and it is not worthy to merge it .
>
> so assume we should hold your patch as it could cause some regression.
>
> Thanks
>
> Yinghai
>
> .
>
--
Thanks!
Yijing
prev parent reply other threads:[~2013-04-16 6:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 9:22 [PATCH 1/3] PCI,acpiphp: use generic pci_hp_add_bridge() Yijing Wang
2013-04-01 9:22 ` [PATCH 2/3] PCI: acpiphp: remove unused function acpiphp_max_busnr Yijing Wang
2013-04-01 9:22 ` [PATCH 3/3] PCI, pciehp: remove check for configure display devices Yijing Wang
2013-04-16 1:49 ` [PATCH 1/3] PCI,acpiphp: use generic pci_hp_add_bridge() Yijing Wang
2013-04-16 3:55 ` Yinghai Lu
2013-04-16 6:43 ` Yijing Wang [this message]
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=516CF325.40604@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=yinghai@kernel.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).