mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: liulongfang <liulongfang@huawei.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"jgg@nvidia.com" <jgg@nvidia.com>
Cc: "cohuck@redhat.com" <cohuck@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxarm@openeuler.org" <linuxarm@openeuler.org>
Subject: Re: [PATCH v2 3/5] hisi_acc_vfio_pci: Remove useless function parameter
Date: Sat, 24 Sep 2022 09:45:41 +0800	[thread overview]
Message-ID: <5f6c62a5-9ccf-c130-7285-aa8cedbf65c9@huawei.com> (raw)
In-Reply-To: <d98867217f4047709de00d610ad2e8b8@huawei.com>

On 2022/9/23 18:30, Shameerali Kolothum Thodi wrote:
> 
> 
>> -----Original Message-----
>> From: liulongfang
>> Sent: 22 September 2022 09:39
>> To: alex.williamson@redhat.com; jgg@nvidia.com; Shameerali Kolothum
>> Thodi <shameerali.kolothum.thodi@huawei.com>
>> Cc: cohuck@redhat.com; linux-kernel@vger.kernel.org;
>> linuxarm@openeuler.org; liulongfang <liulongfang@huawei.com>
>> Subject: [PATCH v2 3/5] hisi_acc_vfio_pci: Remove useless function
>> parameter
>>
>> Remove unused function parameters for vf_qm_fun_reset() and
>> ensure the device is enabled before the reset operation
>> is performed.
>>
>> Signed-off-by: Longfang Liu <liulongfang@huawei.com>
> 
> Hi Longfang,
> 
> This one seems to have a merge conflict on top of vfio/next branch.
> May be better to rebase and send a v3 picking up Jason's R-by as well?
> 

I merged this patchset to the latest tag version vfio-v6.0-rc5 of the
vfio/next branch, and there is no merge conflict.

Which patchset do you refer to as "Jason's R-by"? Can you provide the
title of this patchset?

> Thanks,
> Shameer
> 
>> ---
>>  drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 8 +++++---
>>  1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> index 0638a8a6b0c1..24c03ff41502 100644
>> --- a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> +++ b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> @@ -345,8 +345,7 @@ static struct hisi_acc_vf_core_device
>> *hssi_acc_drvdata(struct pci_dev *pdev)
>>  			    core_device);
>>  }
>>
>> -static void vf_qm_fun_reset(struct hisi_acc_vf_core_device *hisi_acc_vdev,
>> -			    struct hisi_qm *qm)
>> +static void vf_qm_fun_reset(struct hisi_qm *qm)
>>  {
>>  	int i;
>>
>> @@ -662,7 +661,10 @@ static void hisi_acc_vf_start_device(struct
>> hisi_acc_vf_core_device *hisi_acc_vd
>>  	if (hisi_acc_vdev->vf_qm_state != QM_READY)
>>  		return;
>>
>> -	vf_qm_fun_reset(hisi_acc_vdev, vf_qm);
>> +	/* Make sure the device is enabled */
>> +	qm_dev_cmd_init(vf_qm);
>> +
>> +	vf_qm_fun_reset(vf_qm);
>>  }
>>
>>  static int hisi_acc_vf_load_state(struct hisi_acc_vf_core_device
>> *hisi_acc_vdev)
>> --
>> 2.33.0
> 
> .
> 

  reply	other threads:[~2022-09-24  1:45 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 [this message]
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=5f6c62a5-9ccf-c130-7285-aa8cedbf65c9@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®