public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Joshua Daley <jdaley@linux.ibm.com>, linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
	mst@redhat.com, jasowang@redhat.com, pbonzini@redhat.com,
	stefanha@redhat.com, eperezma@redhat.com,
	James.Bottomley@HansenPartnership.com,
	martin.petersen@oracle.com, farman@linux.ibm.com,
	frankja@linux.ibm.com
Subject: Re: [PATCH v2 2/3] scsi: virtio_scsi: remove unnecessary fn declaration
Date: Mon, 16 Mar 2026 09:55:15 -0400	[thread overview]
Message-ID: <94050d3a-a7a2-40a9-9da7-38f759fc27f7@linux.ibm.com> (raw)
In-Reply-To: <20260312174256.1557045-3-jdaley@linux.ibm.com>

On 3/12/26 1:42 PM, Joshua Daley wrote:
> virtscsi_handle_event() is not used before its definition, so remove
> a prior declaration.
> 
> Suggested-by: Eric Farman <farman@linux.ibm.com>
> Signed-off-by: Joshua Daley <jdaley@linux.ibm.com>
> ---
>  drivers/scsi/virtio_scsi.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
> index 982f49bc6c69..6efbeaa30f65 100644
> --- a/drivers/scsi/virtio_scsi.c
> +++ b/drivers/scsi/virtio_scsi.c
> @@ -233,8 +233,6 @@ static void virtscsi_ctrl_done(struct virtqueue *vq)
>  	virtscsi_vq_done(vscsi, &vscsi->ctrl_vq, virtscsi_complete_free);
>  };
>  
> -static void virtscsi_handle_event(struct work_struct *work);
> -

Hi Josh,

You can't make this change until after patch 3 where you move the reference to virtscsi_handle_event further down.

In other words, if you just apply patch 1 + this patch you will get:

drivers/scsi/virtio_scsi.c:383:13: warning: ‘virtscsi_handle_event’ defined but not used [-Wunused-function]

until you also apply patch 3.  This breaks bisectability.

Please either re-arrange this series so that this is the last patch OR squash patch 2 + 3 together.

If you choose the latter approach and keep this patch then you can also include:

Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>

>  static int virtscsi_kick_event(struct virtio_scsi *vscsi,
>  			       struct virtio_scsi_event_node *event_node)
>  {


  reply	other threads:[~2026-03-16 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12 17:42 [PATCH v2 0/3] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_init Joshua Daley
2026-03-12 17:42 ` [PATCH v2 1/3] scsi: virtio_scsi: kick event_list unconditionally Joshua Daley
2026-03-16 14:37   ` Matthew Rosato
2026-03-12 17:42 ` [PATCH v2 2/3] scsi: virtio_scsi: remove unnecessary fn declaration Joshua Daley
2026-03-16 13:55   ` Matthew Rosato [this message]
2026-03-16 14:55     ` Joshua Daley
2026-03-12 17:42 ` [PATCH v2 3/3] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_init Joshua Daley
2026-03-16 14:37   ` Matthew Rosato
2026-03-14  7:10 ` [PATCH v2 0/3] " Stefan Hajnoczi

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=94050d3a-a7a2-40a9-9da7-38f759fc27f7@linux.ibm.com \
    --to=mjrosato@linux.ibm.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=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=stefanha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox