From: Alex Williamson <alex@shazbot.org>
To: Longfang Liu <liulongfang@huawei.com>
Cc: <jgg@nvidia.com>, <jonathan.cameron@huawei.com>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] bugfix some issues under abnormal scenarios.
Date: Thu, 29 Jan 2026 14:58:40 -0700 [thread overview]
Message-ID: <20260129145840.1d49a38e@shazbot.org> (raw)
In-Reply-To: <20260122020205.2884497-1-liulongfang@huawei.com>
On Thu, 22 Jan 2026 10:02:01 +0800
Longfang Liu <liulongfang@huawei.com> wrote:
> In certain reset scenarios, repeated migration scenarios, and error injection
> scenarios, it is essential to ensure that the device driver functions properly.
> Issues arising in these scenarios need to be addressed and fixed
>
> Change v1 -> v2
> Fix the reset state handling issue
>
> Longfang Liu (3):
> hisi_acc_vfio_pci: update status after RAS error
> hisi_acc_vfio_pci: resolve duplicate migration states
> hisi_acc_vfio_pci: fix the queue parameter anomaly issue
>
> Weili Qian (1):
> hisi_acc_vfio_pci: fix VF reset timeout issue
>
> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 30 +++++++++++++++++--
> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.h | 2 ++
> 2 files changed, 29 insertions(+), 3 deletions(-)
>
Applied to vfio next branch for v6.20/v7.0. Thanks,
Alex
next prev parent reply other threads:[~2026-01-29 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 2:02 [PATCH v2 0/4] bugfix some issues under abnormal scenarios Longfang Liu
2026-01-22 2:02 ` [PATCH v2 1/4] hisi_acc_vfio_pci: fix VF reset timeout issue Longfang Liu
2026-01-22 2:02 ` [PATCH v2 2/4] hisi_acc_vfio_pci: update status after RAS error Longfang Liu
2026-01-22 2:02 ` [PATCH v2 3/4] hisi_acc_vfio_pci: resolve duplicate migration states Longfang Liu
2026-01-22 2:02 ` [PATCH v2 4/4] hisi_acc_vfio_pci: fix the queue parameter anomaly issue Longfang Liu
2026-01-29 21:58 ` Alex Williamson [this message]
2026-01-30 2:08 ` [PATCH v2 0/4] bugfix some issues under abnormal scenarios liulongfang
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=20260129145840.1d49a38e@shazbot.org \
--to=alex@shazbot.org \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@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