From: Zefan Li <lizefan@huawei.com>
To: Dirk Behme <dirk.behme@gmail.com>
Cc: <stable@vger.kernel.org>
Subject: Re: 3.4.107: Wrong back port of "PCI: Handle read-only BARs on AMD CS553x devices"?
Date: Mon, 15 Jun 2015 11:26:46 +0800 [thread overview]
Message-ID: <557E45F6.6000004@huawei.com> (raw)
In-Reply-To: <55445FDD.8020804@gmail.com>
On 2015/5/2 13:25, Dirk Behme wrote:
> Hi,
>
> from a private 3.4.107 review I've got the comment that
>
> PCI: Handle read-only BARs on AMD CS553x devices
>
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=d4e393820d2ed20fc6a4088f3eda44458764d997
>
> might be wrongly back ported to 3.4.107: The problem is that the prototype of pcibios_bus_to_resource() was changed by commit fc27985 "PCI: Convert pcibios_resource_to_bus() to take a pci_bus, not a pci_dev" in v3.14, but this commit was not back ported to the v3.4.y stable series [1].
>
I've backported fc27985 to 3.4 to fix this. Thanks!
> Best regards
>
> Dirk
>
> [1]
>
> drivers/pci/quirks.c: In function ‘quirk_io’:
> drivers/pci/quirks.c:351:26: warning: passing argument 1 of ‘pcibios_bus_to_resource’ from incompatible pointer type
> pcibios_bus_to_resource(dev->bus, res, &bus_region);
> ^
> In file included from drivers/pci/quirks.c:21:0:
> include/linux/pci.h:653:6: note: expected ‘struct pci_dev *’ but argument is of type ‘struct pci_bus *’
> void pcibios_bus_to_resource(struct pci_dev *dev, struct resource *res,
> ^
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-06-15 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 5:25 3.4.107: Wrong back port of "PCI: Handle read-only BARs on AMD CS553x devices"? Dirk Behme
2015-06-15 3:26 ` Zefan Li [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=557E45F6.6000004@huawei.com \
--to=lizefan@huawei.com \
--cc=dirk.behme@gmail.com \
--cc=stable@vger.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.