From: Jason Gunthorpe <jgg@nvidia.com>
To: Longfang Liu <liulongfang@huawei.com>
Cc: alex.williamson@redhat.com, shameerali.kolothum.thodi@huawei.com,
cohuck@redhat.com, linux-kernel@vger.kernel.org,
linuxarm@openeuler.org
Subject: Re: [PATCH v2 0/5] Fix some bugs and clean code issues
Date: Thu, 22 Sep 2022 11:18:29 -0300 [thread overview]
Message-ID: <YyxutTFZvRyuyWPd@nvidia.com> (raw)
In-Reply-To: <20220922083928.58797-1-liulongfang@huawei.com>
On Thu, Sep 22, 2022 at 04:39:23PM +0800, Longfang Liu wrote:
> Modify two code bugs inside the driver, update the format of the
> driver's log and comments, and delete an unused macro definition.
>
> Longfang Liu (5):
> hisi_acc_vfio_pci: Fixes error return code issue
> hisi_acc_vfio_pci: Fix device data address combination problem
> hisi_acc_vfio_pci: Remove useless function parameter
> hisi_acc_vfio_pci: Remove useless macro definitions
> hisi_acc_vfio_pci: Update some log and comment formats
>
> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 36 ++++++++++---------
> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.h | 7 ++--
> 2 files changed, 22 insertions(+), 21 deletions(-)
For the series
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
prev parent reply other threads:[~2022-09-22 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 8:39 [PATCH v2 0/5] Fix some bugs and clean code issues Longfang Liu
2022-09-22 8:39 ` [PATCH v2 1/5] hisi_acc_vfio_pci: Fixes error return code issue Longfang Liu
2022-09-22 8:39 ` [PATCH v2 2/5] hisi_acc_vfio_pci: Fix device data address combination problem Longfang Liu
2022-09-22 8:39 ` [PATCH v2 3/5] hisi_acc_vfio_pci: Remove useless function parameter Longfang Liu
2022-09-23 10:30 ` Shameerali Kolothum Thodi
2022-09-24 1:45 ` liulongfang
2022-09-24 1:49 ` liulongfang
2022-09-22 8:39 ` [PATCH v2 4/5] hisi_acc_vfio_pci: Remove useless macro definitions Longfang Liu
2022-09-22 8:39 ` [PATCH v2 5/5] hisi_acc_vfio_pci: Update some log and comment formats Longfang Liu
2022-09-22 14:18 ` Jason Gunthorpe [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=YyxutTFZvRyuyWPd@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=liulongfang@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.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