linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Simon Horman" <horms+renesas@verge.net.au>,
	"Christian König" <christian.koenig@amd.com>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Ingo Molnar" <mingo@kernel.org>
Subject: [GIT PULL] PCI fixes for v4.15
Date: Thu, 14 Dec 2017 17:34:08 -0600	[thread overview]
Message-ID: <20171214233408.GA68544@bhelgaas-glaptop.roam.corp.google.com> (raw)

PCI fixes:

  - add a pci_get_domain_bus_and_slot() stub for the CONFIG_PCI=n case to
    avoid build breakage in the v4.16 merge window if a
    pci_get_bus_and_slot() -> pci_get_domain_bus_and_slot() patch gets
    merged before the PCI tree (Randy Dunlap)

  - fix an AMD boot regression in the 64bit BAR support added in v4.15
    (Christian König)

  - fix an R-Car use-after-free that causes a crash if no PCIe card is
    present (Geert Uytterhoeven)


The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:

  Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.15-fixes-1

for you to fetch changes up to 0c31f1d7be1b5c4858b1d714dcefa25f41428cab:

  PCI: rcar: Fix use-after-free in probe error path (2017-12-12 11:01:47 -0600)

----------------------------------------------------------------
pci-v4.15-fixes-1

----------------------------------------------------------------
Christian König (2):
      x86/PCI: Fix infinite loop in search for 64bit BAR placement
      x86/PCI: Only enable a 64bit BAR on single-socket AMD Family 15h

Geert Uytterhoeven (1):
      PCI: rcar: Fix use-after-free in probe error path

Randy Dunlap (1):
      PCI: Add pci_get_domain_bus_and_slot() stub

 arch/x86/pci/fixup.c         | 27 +++++++++++++++++++++------
 drivers/pci/host/pcie-rcar.c |  8 ++++----
 include/linux/pci.h          |  3 +++
 3 files changed, 28 insertions(+), 10 deletions(-)

             reply	other threads:[~2017-12-14 23:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 23:34 Bjorn Helgaas [this message]
2018-01-12 20:22 [GIT PULL] PCI fixes for v4.15 Bjorn Helgaas
2018-01-23 19:56 Bjorn Helgaas
2018-01-23 20:49 ` Linus Torvalds
2018-01-23 20:53   ` Linus Torvalds
2018-01-24  0:46   ` Bjorn Helgaas
2018-01-24  1:04     ` Linus Torvalds
2018-01-24  7:17       ` Andy Shevchenko
2018-01-24 16:20       ` Bjorn Helgaas
2018-01-24 16:40         ` Linus Torvalds
2018-01-24 17:27           ` Christian König
2018-01-24 20:25           ` Peter Grayson
2018-01-24 20:48             ` Linus Torvalds
2018-01-24 16:45       ` Peter Grayson

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=20171214233408.GA68544@bhelgaas-glaptop.roam.corp.google.com \
    --to=helgaas@kernel.org \
    --cc=arnd@arndb.de \
    --cc=christian.koenig@amd.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mingo@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.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).