mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Longfang Liu <liulongfang@huawei.com>
To: <alex.williamson@redhat.com>, <jgg@nvidia.com>,
	<shameerali.kolothum.thodi@huawei.com>
Cc: <cohuck@redhat.com>, <linux-kernel@vger.kernel.org>,
	<linuxarm@openeuler.org>, <liulongfang@huawei.com>
Subject: [PATCH v2 0/5] Fix some bugs and clean code issues
Date: Thu, 22 Sep 2022 16:39:23 +0800	[thread overview]
Message-ID: <20220922083928.58797-1-liulongfang@huawei.com> (raw)

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(-)

-- 
2.33.0


             reply	other threads:[~2022-09-22  8:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  8:39 Longfang Liu [this message]
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 ` [PATCH v2 0/5] Fix some bugs and clean code issues Jason 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=20220922083928.58797-1-liulongfang@huawei.com \
    --to=liulongfang@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --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

all inboxes | Powered by JetHome®