From: Arnd Bergmann <arnd@arndb.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Joachim Nilsson <troglobit@gmail.com>,
linux-pci@vger.kernel.org, Rob Herring <robh@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: [PATCH] pci-versatile.c: Update for API change in list_for_each_entry()
Date: Wed, 25 Feb 2015 16:15:02 +0100 [thread overview]
Message-ID: <5150533.nuGgOOyLIn@wuerfel> (raw)
From: Joachim Nilsson <troglobit@gmail.com>
In Linux 4.0-rc1 ARM Versatile PCI build fails to build due to what
appears to be an API update. This patch is a very simple correction,
merely posted as a heads-up to the maintainers. Hopefully a better
fix can be forwarded to Linus.
[arnd: the patch actually looks correct, so let's take this version]
Signed-off-by: Joachim Nilsson <troglobit@gmail.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
Joachim reported the bug, and I independently found the same problem.
The patch he sent to the list did not apply for me for an unknown reason,
but I fixed it up and forward it now to the right list of recipients.
diff --git a/drivers/pci/host/pci-versatile.c b/drivers/pci/host/pci-versatile.c
index 1ec694a52379..464bf492ee2a 100644
--- a/drivers/pci/host/pci-versatile.c
+++ b/drivers/pci/host/pci-versatile.c
@@ -80,7 +80,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) {
struct resource *parent, *res = win->res;
switch (resource_type(res)) {
next reply other threads:[~2015-02-25 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 15:15 Arnd Bergmann [this message]
2015-02-26 7:41 ` [PATCH] pci-versatile.c: Update for API change in list_for_each_entry() Linus Walleij
2015-02-26 15:45 ` Rafael J. Wysocki
2015-02-26 23:35 ` Bjorn Helgaas
2015-02-28 0:11 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2015-02-24 8:26 Troglobit
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=5150533.nuGgOOyLIn@wuerfel \
--to=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robh@kernel.org \
--cc=troglobit@gmail.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 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.