From: "Jingoo Han" <jingoohan1@gmail.com>
To: "'Yijing Wang'" <wangyijing@huawei.com>,
"'Bjorn Helgaas'" <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, "'Daniel Axtens'" <dja@axtens.net>,
"'Arnd Bergmann'" <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>,
"'Mohit Kumar'" <mohit.kumar@st.com>,
"'Pratyush Anand'" <pratyush.anand@gmail.com>,
"'Lucas Stach'" <l.stach@pengutronix.de>
Subject: Re: [PATCH Part1 v11 3/5] PCI: designware: Use pci_scan_root_bus() for simplicity
Date: Wed, 27 May 2015 23:18:37 +0900 [thread overview]
Message-ID: <000301d09888$09d01370$1d703a50$@com> (raw)
On Tue, 28 Apr 2015 15:01:37 +0800, Yijing Wang wrote:
> Pci_bus_add_devices() was ripped out of pci_scan_root_bus().
> Now pci_scan_root_bus() == pci_create_root_bus() +
> pci_scan_child_bus() if busn resource is supplied.
> Designware added the busn resource to resources list
> in dw_pcie_setup(). So it should be safe to use
> pci_scan_root_bus() instead.
>
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> CC: Mohit Kumar <mohit.kumar@st.com>
> CC: Jingoo Han <jg1.han@samsung.com>
+cc: Pratyush Anand, Lucas Stach
Acked-by: Jingoo Han <jingoohan1@gmail.com>
> ---
> drivers/pci/host/pcie-designware.c | 4 +---
> 1 files changed, 1 insertions(+), 3 deletions(-)
next reply other threads:[~2015-05-27 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 14:18 Jingoo Han [this message]
2015-06-03 11:45 ` [PATCH Part1 v11 3/5] PCI: designware: Use pci_scan_root_bus() for simplicity Pratyush Anand
-- strict thread matches above, loose matches on Subject: below --
2015-04-28 7:01 [PATCH Part1 v11 0/5] Some cleanup for pcie host drivers Yijing Wang
2015-04-28 7:01 ` [PATCH Part1 v11 3/5] PCI: designware: Use pci_scan_root_bus() for simplicity Yijing Wang
2015-04-28 8:15 ` Lucas Stach
2015-05-27 0:12 ` Bjorn Helgaas
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='000301d09888$09d01370$1d703a50$@com' \
--to=jingoohan1@gmail.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=dja@axtens.net \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=mohit.kumar@st.com \
--cc=pratyush.anand@gmail.com \
--cc=wangyijing@huawei.com \
/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).