From: Bjorn Helgaas <bhelgaas@google.com>
To: linux-pci@vger.kernel.org
Cc: David Airlie <airlied@linux.ie>, Bodo Eggert <7eggert@gmx.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] x86/PCI HPET bugfix and other cleanups
Date: Fri, 25 Apr 2014 11:16:23 -0600 [thread overview]
Message-ID: <20140425171144.312.9601.stgit@bhelgaas-glaptop.roam.corp.google.com> (raw)
The first two are intended as a bugfix for a very old regression:
https://bugzilla.kernel.org/show_bug.cgi?id=68591 "pci=nocrs required to
boot Asrock M3A UCC". Without "pci=nocrs", the system hangs during boot
when the PCI core moves the HPET. Unfortunately I do not have testing
results from the reporter (ping, Bodo :)).
The third and fourth are minor cleanups, no functional change intended
except for the format of some AGP printks.
I intend these for v3.16.
---
Bjorn Helgaas (4):
x86/PCI: Don't try to move IORESOURCE_PCI_FIXED resources
x86/PCI: Mark HPET BAR as IORESOURCE_PCI_FIXED
x86/PCI: Move pcibios_assign_resources() annotation to definition
x86/gart: Tidy messages and add bridge device info
arch/x86/kernel/aperture_64.c | 20 ++++++++++++--------
arch/x86/pci/fixup.c | 12 ++++++++++++
arch/x86/pci/i386.c | 27 ++++++++++++++++-----------
3 files changed, 40 insertions(+), 19 deletions(-)
next reply other threads:[~2014-04-25 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 17:16 Bjorn Helgaas [this message]
2014-04-25 17:16 ` [PATCH 1/4] x86/PCI: Don't try to move IORESOURCE_PCI_FIXED resources Bjorn Helgaas
2014-04-25 17:16 ` [PATCH 2/4] x86/PCI: Mark HPET BAR as IORESOURCE_PCI_FIXED Bjorn Helgaas
2014-04-25 17:16 ` [PATCH 3/4] x86/PCI: Move pcibios_assign_resources() annotation to definition Bjorn Helgaas
2014-04-25 17:16 ` [PATCH 4/4] x86/gart: Tidy messages and add bridge device info Bjorn Helgaas
2014-04-26 6:01 ` Ingo Molnar
2014-04-28 23:22 ` Bjorn Helgaas
2014-05-07 18:00 ` Ingo Molnar
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=20140425171144.312.9601.stgit@bhelgaas-glaptop.roam.corp.google.com \
--to=bhelgaas@google.com \
--cc=7eggert@gmx.de \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®