From: Wesley Sheng <wesley.sheng@microchip.com>
To: <kurt.schwemmer@microsemi.com>, <logang@deltatee.com>,
<bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <wesleyshenggit@sina.com>, <wesley.sheng@microchip.com>,
<kelvin.cao@microchip.com>
Subject: [PATCH 0/2] Fix two bugs of switchtec module
Date: Mon, 8 Apr 2019 22:34:46 +0800 [thread overview]
Message-ID: <1554734088-5755-1-git-send-email-wesley.sheng@microchip.com> (raw)
Hi, Everyone,
This patch series fix two bugs of switchtec module.
The first is introduced by device spec definition issue: the maximum
supported PCIe function number by hardware should be 255 instead of
the false number of 48. Rectify it in driver and for backward
compatible, a new ioctl and corresponding data structure are created,
while keep the deprecated one.
The second is MRPC event unintentionally masked at corner case.
Fix this bug by skipping the mask operation for MRPC event in event ISR
like what we already do for LINK event.
Regard,
Wesley
Wesley Sheng (2):
switchtec: Fix false maximum supported PCIe function number issue
switchtec: Fix unintended mask of MRPC event
drivers/pci/switch/switchtec.c | 42 +++++++++++++++++++++++++-----------
include/linux/switchtec.h | 2 +-
include/uapi/linux/switchtec_ioctl.h | 13 ++++++++++-
3 files changed, 42 insertions(+), 15 deletions(-)
--
2.7.4
next reply other threads:[~2019-04-08 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 14:34 Wesley Sheng [this message]
2019-04-08 14:34 ` [PATCH 1/2] switchtec: Fix false maximum supported PCIe function number issue Wesley Sheng
2019-04-09 22:36 ` Bjorn Helgaas
2019-04-09 23:32 ` Logan Gunthorpe
2019-04-08 14:34 ` [PATCH 2/2] switchtec: Fix unintended mask of MRPC event Wesley Sheng
2019-04-08 16:00 ` [PATCH 0/2] Fix two bugs of switchtec module Logan Gunthorpe
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=1554734088-5755-1-git-send-email-wesley.sheng@microchip.com \
--to=wesley.sheng@microchip.com \
--cc=bhelgaas@google.com \
--cc=kelvin.cao@microchip.com \
--cc=kurt.schwemmer@microsemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=wesleyshenggit@sina.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;
as well as URLs for NNTP newsgroup(s).