From: Yijing Wang <wangyijing@huawei.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Rob Herring <robh@kernel.org>, <jiang.liu@linux.intel.com>,
<linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: versatile: Fix building error for resource_list_for_each_entry
Date: Fri, 20 Mar 2015 09:18:50 +0800 [thread overview]
Message-ID: <550B757A.4090502@huawei.com> (raw)
In-Reply-To: <20150319155920.GG26935@google.com>
On 2015/3/19 23:59, Bjorn Helgaas wrote:
> On Mon, Mar 16, 2015 at 11:11:03AM +0800, Yijing Wang wrote:
>> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
>> ---
>> drivers/pci/host/pci-versatile.c | 3 ++-
>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/pci/host/pci-versatile.c b/drivers/pci/host/pci-versatile.c
>> index e3a2450..4352ee9 100644
>> --- a/drivers/pci/host/pci-versatile.c
>> +++ b/drivers/pci/host/pci-versatile.c
>> @@ -22,6 +22,7 @@
>> #include <linux/of_platform.h>
>> #include <linux/pci.h>
>> #include <linux/platform_device.h>
>> +#include <linux/resource_ext.h>
>>
>> static void __iomem *versatile_pci_base;
>> static void __iomem *versatile_cfg_base[2];
>> @@ -80,7 +81,7 @@ static int versatile_pci_parse_request_of_pci_ranges(struct device *dev,
>> if (err)
>> return err;
>>
>> - resource_list_for_each_entry(win, res, list) {
>> + resource_list_for_each_entry(win, res) {
>
> This fix appeared in v4.0-rc3 as f1651a242809 ("PCI: versatile: Update for
> list_for_each_entry() API change").
>
> Rafael merged it through his tree because I think the problem happened in
> 872912352c5b ("Merge tag 'pm+acpi-3.20-rc1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm") where the
> conflict resolution changed list_for_each_entry() to
> resource_list_for_each_entry() but forgot to drop the extra parameter.
>
> I rebased my "next" branch to v4.0-rc4, which picks up that fix.
OK, thanks!
>
>
>> struct resource *parent, *res = win->res;
>>
>> switch (resource_type(res)) {
>> --
>> 1.7.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Thanks!
Yijing
prev parent reply other threads:[~2015-03-20 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 3:11 [PATCH] PCI: versatile: Fix building error for resource_list_for_each_entry Yijing Wang
2015-03-19 15:59 ` Bjorn Helgaas
2015-03-20 1:18 ` 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=550B757A.4090502@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=robh@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 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.