From: Logan Gunthorpe <logang@deltatee.com>
To: kelvin.cao@microchip.com, kurt.schwemmer@microsemi.com,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: kelvincao@outlook.com
Subject: Re: [PATCH 0/5] Switchtec Fixes and Improvements
Date: Fri, 24 Sep 2021 09:53:27 -0600 [thread overview]
Message-ID: <b4908c93-fb43-001b-b3eb-d3da0bb377c9@deltatee.com> (raw)
In-Reply-To: <20210924110842.6323-1-kelvin.cao@microchip.com>
On 2021-09-24 5:08 a.m., kelvin.cao@microchip.com wrote:
> From: Kelvin Cao <kelvin.cao@microchip.com>
>
> Hi,
>
> Please find a bunch of patches for the switchtec driver collected over the
> last few months.
>
> The first 2 patches fix two minor bugs. Patch 3 updates the method of
> getting management VEP instance ID based on a new firmware change. Patch
> 4 replaces ENOTSUPP with EOPNOTSUPP to follow the preference of kernel.
> And the last patch adds check of event support to align with new firmware
> implementation.
>
> This patchset is based on v5.15-rc2.
>
> Thanks,
> Kelvin
>
> Kelvin Cao (4):
> PCI/switchtec: Error out MRPC execution when no GAS access
> PCI/switchtec: Fix a MRPC error status handling issue
> PCI/switchtec: Update the way of getting management VEP instance ID
> PCI/switchtec: Replace ENOTSUPP with EOPNOTSUPP
>
> Logan Gunthorpe (1):
> PCI/switchtec: Add check of event support
>
> drivers/pci/switch/switchtec.c | 87 +++++++++++++++++++++++++++-------
> include/linux/switchtec.h | 1 +
> 2 files changed, 71 insertions(+), 17 deletions(-)
Thanks Kelvin! This all looks good to me.
For the entire series (except the last patch which I wrote):
Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
Logan
next prev parent reply other threads:[~2021-09-24 15:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 11:08 [PATCH 0/5] Switchtec Fixes and Improvements kelvin.cao
2021-09-24 11:08 ` [PATCH 1/5] PCI/switchtec: Error out MRPC execution when no GAS access kelvin.cao
2021-10-01 20:18 ` Bjorn Helgaas
2021-10-01 20:29 ` Logan Gunthorpe
2021-10-01 23:49 ` Kelvin.Cao
2021-10-02 15:11 ` Bjorn Helgaas
2021-10-04 20:51 ` Kelvin.Cao
2021-10-05 20:11 ` Bjorn Helgaas
2021-10-06 0:37 ` Kelvin.Cao
2021-10-06 2:33 ` Bjorn Helgaas
2021-10-06 5:49 ` Kelvin.Cao
2021-10-06 14:19 ` Bjorn Helgaas
2021-10-06 19:00 ` Kelvin.Cao
2021-10-06 20:20 ` Bjorn Helgaas
2021-10-06 21:27 ` Kelvin.Cao
2021-10-07 21:23 ` Bjorn Helgaas
2021-10-08 0:06 ` Kelvin.Cao
2021-10-08 11:03 ` Bjorn Helgaas
2021-10-01 22:58 ` Kelvin.Cao
2021-10-01 23:52 ` Logan Gunthorpe
2021-10-02 0:05 ` Kelvin.Cao
2021-09-24 11:08 ` [PATCH 2/5] PCI/switchtec: Fix a MRPC error status handling issue kelvin.cao
2021-09-24 11:08 ` [PATCH 3/5] PCI/switchtec: Update the way of getting management VEP instance ID kelvin.cao
2021-09-24 11:08 ` [PATCH 4/5] PCI/switchtec: Replace ENOTSUPP with EOPNOTSUPP kelvin.cao
2021-09-24 11:08 ` [PATCH 5/5] PCI/switchtec: Add check of event support kelvin.cao
2021-09-24 15:53 ` Logan Gunthorpe [this message]
2021-09-25 5:27 ` [PATCH 0/5] Switchtec Fixes and Improvements Kelvin.Cao
2021-09-27 16:39 ` Bjorn Helgaas
2021-09-27 18:25 ` Kelvin.Cao
2021-10-08 17:05 ` Bjorn Helgaas
2021-10-08 17:23 ` Logan Gunthorpe
2021-10-08 18:25 ` 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=b4908c93-fb43-001b-b3eb-d3da0bb377c9@deltatee.com \
--to=logang@deltatee.com \
--cc=bhelgaas@google.com \
--cc=kelvin.cao@microchip.com \
--cc=kelvincao@outlook.com \
--cc=kurt.schwemmer@microsemi.com \
--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).