From: <Kelvin.Cao@microchip.com>
To: <helgaas@kernel.org>
Cc: <kurt.schwemmer@microsemi.com>, <bhelgaas@google.com>,
<kelvincao@outlook.com>, <logang@deltatee.com>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] Switchtec Fixes and Improvements
Date: Thu, 14 Oct 2021 21:19:54 +0000 [thread overview]
Message-ID: <13fce38663833bb9dd521b46abc19312064794a0.camel@microchip.com> (raw)
In-Reply-To: <20211014144740.GA2028709@bhelgaas>
On Thu, 2021-10-14 at 09:47 -0500, Bjorn Helgaas wrote:
> On Thu, Oct 14, 2021 at 02:18:54PM +0000, kelvin.cao@microchip.com
> wrote:
> > From: Kelvin Cao <kelvin.cao@microchip.com>
> >
> > Hi,
> >
> > This patchset is mainly for improving the commit message of [PATCH
> > 1/5]
> > in v1[1] to elaborate the root cause, together with a function
> > renaming
> > and some other tweaks.
> >
> > This patchset is based on v5.15-rc5.
>
> Applied, replacing the previous set, thanks!
Thank you Bjorn!
>
> > [1]
> > https://lore.kernel.org/lkml/20210924110842.6323-1-kelvin.cao@microchip.com/
> >
> > Changes since v1:
> > - Rebase on 5.15-rc5
> > - Tweak some comment spacing (as suggested by Bjorn)
> > - Update commit message to elaborate the root cause of MRPC
> > execution
> > hanging (as suggested by Bjorn)
> > - Rename function check_access() to is_firmware_running()
> > (as suggested by Logan) so the function name suggests the meaning
> > of
> > the return values (as suggested by Bjorn)
> > - Add comment to function is_firmware_running() (as suggested by
> > Logan)
> >
> >
> > Kelvin Cao (4):
> > PCI/switchtec: Error out MRPC execution when MMIO reads fail
> > 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 | 95 ++++++++++++++++++++++++++++
> > ------
> > include/linux/switchtec.h | 1 +
> > 2 files changed, 79 insertions(+), 17 deletions(-)
> >
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2021-10-14 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 14:18 [PATCH v2 0/5] Switchtec Fixes and Improvements kelvin.cao
2021-10-14 14:18 ` [PATCH v2 1/5] PCI/switchtec: Error out MRPC execution when MMIO reads fail kelvin.cao
2021-10-15 1:21 ` Krzysztof Wilczyński
2021-10-15 22:13 ` Kelvin.Cao
2021-10-14 14:18 ` [PATCH v2 2/5] PCI/switchtec: Fix a MRPC error status handling issue kelvin.cao
2021-10-14 14:18 ` [PATCH v2 3/5] PCI/switchtec: Update the way of getting management VEP instance ID kelvin.cao
2021-10-14 14:18 ` [PATCH v2 4/5] PCI/switchtec: Replace ENOTSUPP with EOPNOTSUPP kelvin.cao
2021-10-15 1:55 ` Krzysztof Wilczyński
2021-10-14 14:18 ` [PATCH v2 5/5] PCI/switchtec: Add check of event support kelvin.cao
2021-10-14 14:47 ` [PATCH v2 0/5] Switchtec Fixes and Improvements Bjorn Helgaas
2021-10-14 21:19 ` Kelvin.Cao [this message]
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=13fce38663833bb9dd521b46abc19312064794a0.camel@microchip.com \
--to=kelvin.cao@microchip.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kelvincao@outlook.com \
--cc=kurt.schwemmer@microsemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.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).