All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Marquardt <davemarq@linux.ibm.com>
To: sashiko-bot@kernel.org
Cc: sashiko-reviews@lists.linux.dev, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v13 11/11] scsi: ibmvfc: handle extended FPIN events
Date: Wed, 07 Oct 2026 14:52:22 -0500	[thread overview]
Message-ID: <87o6d5b85l.fsf@linux.ibm.com> (raw)
In-Reply-To: <sashiko-outbox-163310@kernel.org> (sashiko-bot@kernel.org's message of "Wed, 07 Oct 2026 19:33:54 +0000")

sashiko-bot@kernel.org writes:

> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] scsi: ibmvscsi: unused list head variable `evt_doneq` in test
> --
>
> commit 7276d45825dded3ce9d906eb91c3d06e314dc430
> Author: Dave Marquardt <davemarq@linux.ibm.com>
>
>     scsi: ibmvfc: handle extended FPIN events
>
> This commit implements support for extended FPIN messages via the
> asynchronous sub-queue. It introduces new capabilities and unit tests for
> extended FPIN event handling.
>
>> diff --git a/drivers/scsi/ibmvscsi/ibmvfc_kunit.c b/drivers/scsi/ibmvscsi/ibmvfc_kunit.c
>> index d2ef35e928eae..cc6e6d0b5f963 100644
>> --- a/drivers/scsi/ibmvscsi/ibmvfc_kunit.c
>> +++ b/drivers/scsi/ibmvscsi/ibmvfc_kunit.c
>
> [ ... ]
>
>> +/**
>> + * ibmvfc_extended_fpin_test - unit test for extended FPIN events
>> + * @test: pointer to kunit structure
>> + *
>> + * Return: void
>> + */
>> +static void ibmvfc_extended_fpin_test(struct kunit *test)
>> +{
>> +	enum ibmvfc_ae_fpin_status fs;
>> +	struct ibmvfc_async_subq_fpin crq;
>> +	struct ibmvfc_target *tgt;
>> +	struct ibmvfc_host *vhost;
>> +	struct fc_host_attrs *fc_host;
>> +	struct fc_rport *rport;
>> +	LIST_HEAD(evt_doneq);
>
> [Severity: Low]
> Is the evt_doneq list head needed? The variable is declared and initialized
> at the beginning of ibmvfc_extended_fpin_test(), but it doesn't appear to be
> used anywhere else in the test function body.

I agree, evt_doneq is not needed. I will fix in a v14 series or we can
let this in and I'll fix it separately afterwards.

-Dave

  reply	other threads:[~2026-10-07 19:52 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 19:25 [PATCH v13 00/11] scsi: ibmvfc: make ibmvfc support FPIN messages Dave Marquardt via B4 Relay
2026-10-07 19:25 ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 01/11] scsi: ibmvfc: fix IRQ leak and guard deregister on channel reg failure Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 02/11] scsi: ibmvfc: fix potential clobbering of rc after failed irq setup Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 03/11] scsi: ibmvfc: fix potential NULL pointer dereference on failed queue allocation Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:44   ` sashiko-bot
2026-10-09 18:34     ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 04/11] scsi: ibmvfc: add basic FPIN support Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:41   ` sashiko-bot
2026-10-08 21:24     ` Dave Marquardt
2026-10-09  5:20   ` kernel test robot
2026-10-09 14:45     ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 05/11] scsi: ibmvfc: add NOOP command support Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:36   ` sashiko-bot
2026-10-12 19:24     ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 06/11] scsi: ibmvfc: add FPIN extended flag and async sub-CRQ queue handle Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 07/11] scsi: ibmvfc: extend async event handlers for async sub-CRQ events Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-09 13:22   ` kernel test robot
2026-10-09 14:50     ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 08/11] scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:44   ` sashiko-bot
2026-10-12 19:44     ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 09/11] scsi: ibmvfc: extend channel reg/dereg helpers for async sub-CRQ Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 10/11] scsi: ibmvfc: register and use asynchronous sub CRQ for events Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:42   ` sashiko-bot
2026-10-13 22:02     ` Dave Marquardt
2026-10-07 19:25 ` [PATCH v13 11/11] scsi: ibmvfc: handle extended FPIN events Dave Marquardt via B4 Relay
2026-10-07 19:25   ` Dave Marquardt
2026-10-07 19:33   ` sashiko-bot
2026-10-07 19:52     ` Dave Marquardt [this message]
2026-10-09 20:29   ` kernel test robot
2026-10-12 19:50     ` Dave Marquardt

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=87o6d5b85l.fsf@linux.ibm.com \
    --to=davemarq@linux.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@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.