From: Meelis Roos <mroos@linux.ee>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Yinghai Lu <yinghai@kernel.org>,
linux-pci@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: sparc64 PCI BAR allocation is still problematic
Date: Tue, 10 Apr 2018 21:45:09 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1804102144240.32411@math.ut.ee> (raw)
In-Reply-To: <20180410173437.GB24642@bhelgaas-glaptop.roam.corp.google.com>
> commit bc270e0028cd0856d5689cab38f0071f0d07b3be
> Author: Bjorn Helgaas <bhelgaas@google.com>
> Date: Tue Apr 10 08:47:34 2018 -0500
>=20
> sparc/PCI: Request legacy VGA framebuffer only for VGA devices
Thank you.
It does not seem to compile for me:
CC arch/sparc/kernel/pci.o
arch/sparc/kernel/pci.c: In function =A1pci_claim_legacy_resources=A2:
arch/sparc/kernel/pci.c:644:26: error: =A1bus=A2 undeclared (first use in=
this function)
pcibios_bus_to_resource(bus, p, ®ion);
--=20
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2018-04-10 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 18:44 sparc64 PCI BAR allocation is still problematic Meelis Roos
2018-04-08 21:21 ` David Miller
2018-04-09 3:00 ` Sinan Kaya
2018-04-09 10:47 ` Meelis Roos
2018-04-09 3:23 ` Bjorn Helgaas
2018-04-09 14:30 ` Meelis Roos
2018-04-10 17:34 ` Bjorn Helgaas
2018-04-10 18:45 ` Meelis Roos [this message]
2018-04-10 18:56 ` Bjorn Helgaas
2018-04-11 7:59 ` Meelis Roos
2018-04-11 13:33 ` Bjorn Helgaas
2018-04-11 14:40 ` Meelis Roos
2018-04-11 20:01 ` Bjorn Helgaas
2018-04-11 20:25 ` Meelis Roos
2018-04-11 21:17 ` Bjorn Helgaas
2018-05-21 20:10 ` Bjorn Helgaas
2018-06-20 22:05 ` Bjorn Helgaas
2018-06-29 10:06 ` Meelis Roos
2018-06-29 13:47 ` Bjorn Helgaas
2018-07-06 19:49 ` Meelis Roos
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=alpine.LRH.2.21.1804102144240.32411@math.ut.ee \
--to=mroos@linux.ee \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=yinghai@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 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).