All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Duncan <LDuncan@suse.com>
To: Himanshu Madhani <hmadhani@marvell.com>,
	"James.Bottomley@HansenPartnership.com" 
	<James.Bottomley@HansenPartnership.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/6] qla2xxx: Fix message indicating vectors used by driver
Date: Wed, 4 Sep 2019 22:33:39 +0000	[thread overview]
Message-ID: <2589c49d-fe93-de98-b141-e1ee3e98e46b@suse.com> (raw)
In-Reply-To: <20190830222402.23688-2-hmadhani@marvell.com>

On 8/30/19 3:23 PM, Himanshu Madhani wrote:
> This patch updates log message which indicates number
> of vectors used by driver instead of displaying failure
> to get maximum requested vectors. Driver will always
> request maximum vectors during initialization. In the
> event driver is not able to get maximum requested vectors,
> it will adjust the allocated vectors. This is normal and
> does not imply failure in driver.
> 
> Signed-off-by: Himanshu Madhani <hmadhani@marvell.com>
> ---
>  drivers/scsi/qla2xxx/qla_isr.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c
> index d81b5ecce24b..4c26630c1c3e 100644
> --- a/drivers/scsi/qla2xxx/qla_isr.c
> +++ b/drivers/scsi/qla2xxx/qla_isr.c
> @@ -3466,10 +3466,8 @@ qla24xx_enable_msix(struct qla_hw_data *ha, struct rsp_que *rsp)
>  		    ha->msix_count, ret);
>  		goto msix_out;
>  	} else if (ret < ha->msix_count) {
> -		ql_log(ql_log_warn, vha, 0x00c6,
> -		    "MSI-X: Failed to enable support "
> -		     "with %d vectors, using %d vectors.\n",
> -		    ha->msix_count, ret);
> +		ql_log(ql_log_info, vha, 0x00c6,
> +		    "MSI-X: Using %d vectors\n", ret);
>  		ha->msix_count = ret;
>  		/* Recalculate queue values */
>  		if (ha->mqiobase && (ql2xmqsupport || ql2xnvmeenable)) {
> 

Reviewed-by: Lee Duncan <lduncan@suse.com>

  parent reply	other threads:[~2019-09-04 22:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 22:23 [PATCH 0/6] qla2xxx: Bug fixes for the driver Himanshu Madhani
2019-08-30 22:23 ` [PATCH 1/6] qla2xxx: Fix message indicating vectors used by driver Himanshu Madhani
2019-09-03 14:46   ` Ewan D. Milne
2019-09-04 22:33   ` Lee Duncan [this message]
2019-08-30 22:23 ` [PATCH 2/6] qla2xxx: Fix flash read for Qlogic ISPs Himanshu Madhani
2019-09-03 14:48   ` Ewan D. Milne
2019-09-13 20:36   ` Martin Wilck
2019-09-13 22:37     ` Martin K. Petersen
2019-09-16 16:19       ` [EXT] " Himanshu Madhani
2019-08-30 22:23 ` [PATCH 3/6] qla2xxx: Fix driver reload for ISP82xx Himanshu Madhani
2019-09-03 14:49   ` Ewan D. Milne
2019-08-30 22:24 ` [PATCH 4/6] qla2xxx: Fix stuck login session Himanshu Madhani
2019-09-03 14:50   ` Ewan D. Milne
2019-08-30 22:24 ` [PATCH 5/6] qla2xxx: Fix stale session Himanshu Madhani
2019-09-03 14:52   ` Ewan D. Milne
2019-08-30 22:24 ` [PATCH 6/6] qla2xxx: Update driver version to 10.01.00.19-k Himanshu Madhani
2019-09-03 14:52   ` Ewan D. Milne
2019-09-07 19:39 ` [PATCH 0/6] qla2xxx: Bug fixes for the driver 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=2589c49d-fe93-de98-b141-e1ee3e98e46b@suse.com \
    --to=lduncan@suse.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hmadhani@marvell.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 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.