From: John Meneghini <jmeneghi@redhat.com>
To: Karan Tilak Kumar <kartilak@cisco.com>, sebaddel@cisco.com
Cc: arulponn@cisco.com, djhawar@cisco.com, gcboffa@cisco.com,
mkai2@cisco.com, satishkh@cisco.com, aeasi@cisco.com,
jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
revers@redhat.com, dan.carpenter@linaro.org
Subject: Re: [PATCH v4 1/5] scsi: fnic: Set appropriate logging level for log message
Date: Fri, 13 Jun 2025 16:34:38 -0400 [thread overview]
Message-ID: <45bc529f-0949-4d3c-a9dd-e7a30eac22ea@redhat.com> (raw)
In-Reply-To: <20250612221805.4066-1-kartilak@cisco.com>
Please move this patch to the end of the series.
The most important change here is:
[PATCH v4 2/5] scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out
This is the major fix and and it should come first. All of these other DEBUG PRINTFs are less important.
Thanks,
/John
On 6/12/25 6:18 PM, Karan Tilak Kumar wrote:
> Replace KERN_INFO with KERN_DEBUG for a log message.
>
> Reviewed-by: Sesidhar Baddela <sebaddel@cisco.com>
> Reviewed-by: Arulprabhu Ponnusamy <arulponn@cisco.com>
> Reviewed-by: Gian Carlo Boffa <gcboffa@cisco.com>
> Reviewed-by: Arun Easi <aeasi@cisco.com>
> Signed-off-by: Karan Tilak Kumar <kartilak@cisco.com>
> ---
> drivers/scsi/fnic/fnic_scsi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/fnic/fnic_scsi.c b/drivers/scsi/fnic/fnic_scsi.c
> index 7133b254cbe4..75b29a018d1f 100644
> --- a/drivers/scsi/fnic/fnic_scsi.c
> +++ b/drivers/scsi/fnic/fnic_scsi.c
> @@ -1046,7 +1046,7 @@ static void fnic_fcpio_icmnd_cmpl_handler(struct fnic *fnic, unsigned int cq_ind
> if (icmnd_cmpl->scsi_status == SAM_STAT_TASK_SET_FULL)
> atomic64_inc(&fnic_stats->misc_stats.queue_fulls);
>
> - FNIC_SCSI_DBG(KERN_INFO, fnic->host, fnic->fnic_num,
> + FNIC_SCSI_DBG(KERN_DEBUG, fnic->host, fnic->fnic_num,
> "xfer_len: %llu", xfer_len);
> break;
>
next prev parent reply other threads:[~2025-06-13 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 22:18 [PATCH v4 1/5] scsi: fnic: Set appropriate logging level for log message Karan Tilak Kumar
2025-06-12 22:18 ` [PATCH v4 2/5] scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out Karan Tilak Kumar
2025-06-12 22:18 ` [PATCH v4 3/5] scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths Karan Tilak Kumar
2025-06-13 21:05 ` John Meneghini
2025-06-13 21:46 ` Karan Tilak Kumar (kartilak)
2025-06-12 22:18 ` [PATCH v4 4/5] scsi: fnic: Turn off FDMI ACTIVE flags on link down Karan Tilak Kumar
2025-06-13 20:28 ` John Meneghini
2025-06-13 21:59 ` Karan Tilak Kumar (kartilak)
2025-06-16 14:35 ` John Meneghini
2025-06-16 16:31 ` Karan Tilak Kumar (kartilak)
2025-06-12 22:18 ` [PATCH v4 5/5] scsi: fnic: Increment driver version number Karan Tilak Kumar
2025-06-13 21:10 ` John Meneghini
2025-06-13 20:34 ` John Meneghini [this message]
2025-06-13 21:45 ` [PATCH v4 1/5] scsi: fnic: Set appropriate logging level for log message Karan Tilak Kumar (kartilak)
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=45bc529f-0949-4d3c-a9dd-e7a30eac22ea@redhat.com \
--to=jmeneghi@redhat.com \
--cc=aeasi@cisco.com \
--cc=arulponn@cisco.com \
--cc=dan.carpenter@linaro.org \
--cc=djhawar@cisco.com \
--cc=gcboffa@cisco.com \
--cc=jejb@linux.ibm.com \
--cc=kartilak@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mkai2@cisco.com \
--cc=revers@redhat.com \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.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