linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: Jean-Phillipe Brucker <jean-philippe.brucker@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Joerg Roedel <joro@8bytes.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ashok Raj <ashok.raj@intel.com>,
	David Woodhouse <dwmw2@infradead.org>,
	iommu@lists.linux-foundation.org
Subject: [PATCH 0/2] Save and restore pci properties to support FLR
Date: Tue, 30 May 2017 09:25:47 -0700	[thread overview]
Message-ID: <1496161549-167468-1-git-send-email-ashok.raj@intel.com> (raw)

Resending Jean's patch so it can be included earlier than his large
SVM commits. Original patch https://patchwork.kernel.org/patch/9593891
was ack'ed by Bjorn. Let's commit these separately since we need
functionality earlier.

Resending this series as requested by Jean.

CQ Tang (1):
  PCI: Save properties required to handle FLR for replay purposes.

Jean-Philippe Brucker (1):
  PCI: Cache PRI and PASID bits in pci_dev

 drivers/pci/ats.c       | 88 ++++++++++++++++++++++++++++++++++++++++---------
 drivers/pci/pci.c       |  3 ++
 include/linux/pci-ats.h | 10 ++++++
 include/linux/pci.h     |  8 +++++
 4 files changed, 94 insertions(+), 15 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-05-30 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 16:25 Ashok Raj [this message]
2017-05-30 16:25 ` [PATCH 1/2] PCI: Cache PRI and PASID bits in pci_dev Ashok Raj
2017-05-30 16:25 ` [PATCH 2/2] PCI: Save properties required to handle FLR for replay purposes Ashok Raj
2017-05-30 19:50   ` Bjorn Helgaas
2017-05-30 18:53     ` Raj, Ashok
2017-05-30 20:58   ` Bjorn Helgaas
2017-05-30 20:58 ` [PATCH 0/2] Save and restore pci properties to support FLR Bjorn Helgaas

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=1496161549-167468-1-git-send-email-ashok.raj@intel.com \
    --to=ashok.raj@intel.com \
    --cc=bhelgaas@google.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jean-philippe.brucker@arm.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.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).