From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: bhelgaas@google.com
Cc: Mike Marciniszyn <mike.marciniszyn@intel.com>,
Andriy Shevchenko <andriy.shevchenko@intel.com>,
jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-pci@vger.kernel.org,
"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
dledford@redhat.com,
Kamenee Arumugam <kamenee.arumugam@intel.com>
Subject: [PATCH for-next 0/2] Allow drivers to configure AER registers
Date: Wed, 10 Apr 2019 05:34:34 -0700 [thread overview]
Message-ID: <20190410123253.26818.37261.stgit@scvm10.sc.intel.com> (raw)
Hi Folks,
Here is a set of patches from Kamenee that adds an API for
configuring AER registers. At least one driver needs to be able to change the
default settings and a patch (2/2) is included here. Sending both to linux-pci
since there really isn't a reason for the first to exist without a user.
However normally changes to the hfi1 driver would flow through linux-rdma.
This series is based on the PCI branch 'next' but I expect would apply the same
to rdma-next as well if we wanted to go that route.
---
Kamenee Arumugam (2):
PCI/AER: Helper function for configuring AER registers
IB/hfi1: Make Unsupported Request error non-fatal
drivers/infiniband/hw/hfi1/pcie.c | 1 +
drivers/pci/pcie/aer.c | 33 +++++++++++++++++++++++++++++++++
include/linux/aer.h | 17 +++++++++++++++++
3 files changed, 51 insertions(+), 0 deletions(-)
--
-Denny
next reply other threads:[~2019-04-10 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 12:34 Dennis Dalessandro [this message]
2019-04-10 12:34 ` [PATCH for-next 1/2] PCI/AER: Helper function for configuring AER registers Dennis Dalessandro
2019-04-10 13:46 ` Andriy Shevchenko
2019-04-10 12:35 ` [PATCH for-next 2/2] IB/hfi1: Make Unsupported Request error non-fatal Dennis Dalessandro
2019-04-10 19:29 ` Bjorn Helgaas
[not found] ` <14063C7AD467DE4B82DEDB5C278E8663BE6A1B14@FMSMSX108.amr.corp.intel.com>
2019-04-11 18:22 ` Arumugam, Kamenee
2019-04-11 18:29 ` Jason Gunthorpe
2019-04-11 20:37 ` Arumugam, Kamenee
2019-04-12 13:55 ` Jason Gunthorpe
2019-04-15 18:47 ` Dennis Dalessandro
2019-04-15 21:46 ` 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=20190410123253.26818.37261.stgit@scvm10.sc.intel.com \
--to=dennis.dalessandro@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=bhelgaas@google.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kamenee.arumugam@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.j.ruhl@intel.com \
--cc=mike.marciniszyn@intel.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.