From: "Jan Kundrát" <jan.kundrat@cesnet.cz>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
Baruch Siach <baruch@tkos.co.il>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Jason Cooper <jason@lakedaemon.net>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [BISECTED] Regression: Solidrun Clearfog Base won't boot since "PCI: mvebu: Only remap I/O space if configured"
Date: Thu, 13 Sep 2018 10:20:45 +0200 [thread overview]
Message-ID: <5ad46fec-a71a-477a-b23f-d20aacfb481d@cesnet.cz> (raw)
In-Reply-To: <20180913094515.351967bb@windsurf>
On čtvrtek 13. září 2018 9:45:15 CEST, Thomas Petazzoni wrote:
> What about something like the below. I tested it, including the error
> case by forcing an -EPROBE_DEFER. The new pci_unmap_io() is modeled
> after pci_unmap_iospace(). Actually, I would prefer to use
> pci_remap_iospace() and pci_unmap_iospace() but for now this API
> doesn't allow overloading the memory type used for the mapping.
Thanks for providing this fix so quickly, Thomas. I can confirm that this
patch -- tested on top of 54eda9df17f3215b9ed16629ee71ea07413efdaf ("Merge
tag 'pci-v4.19-fixes-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci"). Disclaimer: I
have zero familiarity with Linux' PCI code.
Tested-by: Jan Kundrát <jan.kundrat@cesnet.cz>
With kind regards,
Jan
next prev parent reply other threads:[~2018-09-13 8:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 16:11 Jan Kundrát
2018-09-12 18:49 ` Baruch Siach
2018-09-12 18:50 ` Thomas Petazzoni
2018-09-12 19:00 ` Jan Kundrát
2018-09-12 23:10 ` Russell King - ARM Linux
2018-09-13 3:19 ` Baruch Siach
2018-09-13 7:45 ` Thomas Petazzoni
2018-09-13 8:20 ` Jan Kundrát [this message]
2018-09-13 8:42 ` Thomas Petazzoni
2018-09-24 10:02 ` Jan Kundrát
2018-09-24 10:10 ` Thomas Petazzoni
2018-09-24 10:12 ` Russell King - ARM Linux
2018-09-24 10:26 ` Thomas Petazzoni
2018-09-24 11:13 ` Russell King - ARM Linux
2018-09-24 12:12 ` Thomas Petazzoni
2018-09-24 12:46 ` Lorenzo Pieralisi
2018-09-24 13:10 ` Thomas Petazzoni
2018-09-24 14:15 ` Lorenzo Pieralisi
2018-09-24 14:52 ` Thomas Petazzoni
2018-09-24 16:42 ` Lorenzo Pieralisi
2018-10-01 10:56 ` Jan Kundrát
2018-10-01 12:51 ` Thomas Petazzoni
2018-10-01 21:01 ` Bjorn Helgaas
2018-09-25 8:18 ` Andrew Murray
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=5ad46fec-a71a-477a-b23f-d20aacfb481d@cesnet.cz \
--to=jan.kundrat@cesnet.cz \
--cc=baruch@tkos.co.il \
--cc=bhelgaas@google.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=thomas.petazzoni@bootlin.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
all inboxes | Powered by JetHome®