linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Thomas Lendacky" <Thomas.Lendacky@amd.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Ingo Molnar" <mingo@kernel.org>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Martin Hundebøll" <martin@geanix.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"Len Brown" <lenb@kernel.org>,
	linux-acpi@vger.kernel.org
Subject: [GIT PULL] PCI fixes for v4.20
Date: Wed, 14 Nov 2018 00:20:10 -0600	[thread overview]
Message-ID: <20181114062010.GA189193@google.com> (raw)

PCI fixes:

  - Revert a _PXM change that causes silent early boot failure on some AMD
    ThreadRipper systems (Bjorn Helgaas)


The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:

  Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 0d76bcc960e6057750fcf556b65da13f8bbdfd2b:

  Revert "ACPI/PCI: Pay attention to device-specific _PXM node values" (2018-11-13 08:38:17 -0600)

----------------------------------------------------------------
pci-v4.20-fixes-1

----------------------------------------------------------------
Bjorn Helgaas (1):
      Revert "ACPI/PCI: Pay attention to device-specific _PXM node values"

 drivers/pci/pci-acpi.c | 5 -----
 1 file changed, 5 deletions(-)

             reply	other threads:[~2018-11-14  6:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14  6:20 Bjorn Helgaas [this message]
2018-11-14 20:00 ` [GIT PULL] PCI fixes for v4.20 pr-tracker-bot
2018-11-14 20:12   ` Borislav Petkov
2018-11-14 20:16     ` Konstantin Ryabitsev
2018-11-14 21:46       ` Borislav Petkov
2018-11-14 22:21         ` Konstantin Ryabitsev
2018-11-14 22:48           ` Borislav Petkov
2018-11-15  7:12             ` Bjorn Helgaas
2018-11-15  7:53               ` Konstantin Ryabitsev
2018-11-15 15:03                 ` Bjorn Helgaas
2018-11-15 15:54                   ` Konstantin Ryabitsev
2018-11-15 17:27                     ` Bjorn Helgaas
2018-11-15 18:08                       ` Borislav Petkov
2018-11-15 18:13                       ` Konstantin Ryabitsev
  -- strict thread matches above, loose matches on Subject: below --
2018-12-01  5:59 Bjorn Helgaas
2018-12-01 20:05 ` pr-tracker-bot
2018-12-07 20:44 Bjorn Helgaas
2018-12-07 21:10 ` pr-tracker-bot
2018-12-18 21:40 Bjorn Helgaas
2018-12-18 23:55 ` pr-tracker-bot

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=20181114062010.GA189193@google.com \
    --to=helgaas@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=martin@geanix.com \
    --cc=mingo@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --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).