From: Bjorn Helgaas <bhelgaas@google.com>
To: linux-pci@vger.kernel.org
Cc: Lance Ortiz <lance.ortiz@hpe.com>,
Betty Dall <betty.dall@hpe.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Chen Gong <gong.chen@linux.intel.com>,
KeithBuschkeith.busch@intel.com,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>,
Huang Ying <ying.huang@intel.com>,
Vijay Mohan Pandarathil <vijaymohan.pandarathil@hpe.com>,
Jon Derrick <jonathan.derrick@intel.com>
Subject: [PATCH 0/2] PCI/AER: Remove module parameters
Date: Tue, 06 Sep 2016 17:19:22 -0500 [thread overview]
Message-ID: <20160906221522.23655.66321.stgit@bhelgaas-glaptop2.roam.corp.google.com> (raw)
I'd like to remove the aerdriver.nosourceid and aerdriver.forceload kernel
parameters. They seem like basically debugging things that are not really
supportable upstream.
"nosourceid" may have some legitimate uses, but I'd rather it were done via
quirks with the flag Jon Derrick recently added so it happens
automatically, without users having to specify the parameter.
I don't *know* of any actual users of either of these, but obviously that
doesn't mean there are none. Comments welcome.
---
Bjorn Helgaas (2):
PCI/AER: Remove aerdriver.nosourceid kernel parameter
PCI/AER: Remove aerdriver.forceload kernel parameter
Documentation/PCI/pcieaer-howto.txt | 26 +++++++++-----------------
drivers/pci/pcie/aer/aerdrv.c | 7 +------
drivers/pci/pcie/aer/aerdrv.h | 8 --------
drivers/pci/pcie/aer/aerdrv_core.c | 31 ++++---------------------------
4 files changed, 14 insertions(+), 58 deletions(-)
next reply other threads:[~2016-09-06 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 22:19 Bjorn Helgaas [this message]
2016-09-06 22:19 ` [PATCH 1/2] PCI/AER: Remove aerdriver.nosourceid kernel parameter Bjorn Helgaas
2016-09-06 22:20 ` [PATCH 2/2] PCI/AER: Remove aerdriver.forceload " Bjorn Helgaas
2016-09-14 20:30 ` [PATCH 0/2] PCI/AER: Remove module parameters Bjorn Helgaas
2016-09-17 4:49 ` Tang, CQ
2016-09-19 18:11 ` 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=20160906221522.23655.66321.stgit@bhelgaas-glaptop2.roam.corp.google.com \
--to=bhelgaas@google.com \
--cc=KeithBuschkeith.busch@intel.com \
--cc=betty.dall@hpe.com \
--cc=gong.chen@linux.intel.com \
--cc=jonathan.derrick@intel.com \
--cc=lance.ortiz@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=shuahkh@osg.samsung.com \
--cc=vijaymohan.pandarathil@hpe.com \
--cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®