From: Stefan Hajnoczi <stefanha@redhat.com>
To: Joshua Daley <jdaley@linux.ibm.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux.dev, mst@redhat.com,
jasowang@redhat.com, pbonzini@redhat.com, eperezma@redhat.com,
James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com, mjrosato@linux.ibm.com,
farman@linux.ibm.com, frankja@linux.ibm.com
Subject: Re: [PATCH v4 2/2] scsi: virtio_scsi: kick event_list unconditionally
Date: Thu, 26 Mar 2026 10:00:53 -0400 [thread overview]
Message-ID: <20260326140053.GD758087@fedora> (raw)
In-Reply-To: <20260325180857.3675854-3-jdaley@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
On Wed, Mar 25, 2026 at 07:08:57PM +0100, Joshua Daley wrote:
> The event_list processes non-hotplug events (such as LUN capacity
> changes), so remove the conditions that guard the initial kicks in
> _probe() and _restore(), as well as the work cancellation in _remove().
>
> Suggested-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Joshua Daley <jdaley@linux.ibm.com>
> ---
> drivers/scsi/virtio_scsi.c | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-03-26 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 18:08 [PATCH v4 0/2] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_probe Joshua Daley
2026-03-25 18:08 ` [PATCH v4 1/2] " Joshua Daley
2026-03-26 14:00 ` Stefan Hajnoczi
2026-03-25 18:08 ` [PATCH v4 2/2] scsi: virtio_scsi: kick event_list unconditionally Joshua Daley
2026-03-26 14:00 ` Stefan Hajnoczi [this message]
2026-03-27 20:44 ` [PATCH v4 0/2] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_probe Martin K. Petersen
2026-04-03 2:05 ` Martin K. Petersen
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=20260326140053.GD758087@fedora \
--to=stefanha@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=eperezma@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=jdaley@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.