All of lore.kernel.org
 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>,
	Thinh Nguyen <thinh.nguyen@synopsys.com>,
	"Lukas F. Hartmann" <lukas@mntmn.com>,
	Trent Piepho <tpiepho@impinj.com>,
	Lucas Stach <l.stach@pengutronix.de>
Subject: [GIT PULL] PCI fixes for v5.0
Date: Fri, 8 Feb 2019 08:23:53 -0600	[thread overview]
Message-ID: <20190208142353.GV7268@google.com> (raw)

PCI fixes:

  - Work around Synopsys duplicate Device ID (HAPS USB3, NXP i.MX) that
    breaks PCIe on I.MX SoCs (Thinh Nguyen)


The following changes since commit f14bcc0add3abecceca1a3fe538c4ec9566893f3:

  Revert "PCI: armada8k: Add support for gpio controlled reset signal" (2019-01-31 15:07:29 -0600)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.0-fixes-4

for you to fetch changes up to f57a98e1b71357713e44c57268a53d9c803f0626:

  PCI: Work around Synopsys duplicate Device ID (HAPS USB3, NXP i.MX) (2019-02-06 17:17:27 -0600)

----------------------------------------------------------------
pci-v5.0-fixes-4

----------------------------------------------------------------
Thinh Nguyen (1):
      PCI: Work around Synopsys duplicate Device ID (HAPS USB3, NXP i.MX)

 drivers/pci/quirks.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

             reply	other threads:[~2019-02-08 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 14:23 Bjorn Helgaas [this message]
2019-02-09  0:40 ` [GIT PULL] PCI fixes for v5.0 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-01-31 22:03 Bjorn Helgaas
2019-02-01  7:25 ` pr-tracker-bot
2019-01-18 19:07 Bjorn Helgaas
2019-01-18 19:40 ` pr-tracker-bot
2019-01-10 21:31 Bjorn Helgaas
2019-01-11 17:00 ` 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=20190208142353.GV7268@google.com \
    --to=helgaas@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=lukas@mntmn.com \
    --cc=thinh.nguyen@synopsys.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tpiepho@impinj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.