public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Arnd Bergmann <arnd@arndb.de>,
	qla2xxx-upstream@qlogic.com,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Laurence Oberman <loberman@redhat.com>,
	Himanshu Madhani <himanshu.madhani@cavium.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Himanshu Madhani <hmadhani@marvell.com>,
	Quinn Tran <quinn.tran@cavium.com>,
	Hannes Reinecke <hare@suse.de>, Jens Axboe <axboe@kernel.dk>,
	Darren Trapp <darren.trapp@cavium.com>,
	Bill Kuzeja <William.Kuzeja@stratus.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: qla2xxx: fix unused function warning
Date: Mon, 10 Dec 2018 13:01:06 -0800	[thread overview]
Message-ID: <1544475666.185366.378.camel@acm.org> (raw)
In-Reply-To: <20181210205215.2703138-1-arnd@arndb.de>

On Mon, 2018-12-10 at 21:51 +0100, Arnd Bergmann wrote:
> In what seems to be a mismatch between the scsi-fixes branch and
> the scsi-mkp/for-next branch, a newly introduced variable from
> one patch got obsoleted in another one:
> 
> drivers/scsi/qla2xxx/qla_os.c: In function '__qla2x00_abort_all_cmds':
> drivers/scsi/qla2xxx/qla_os.c:1791:11: error: unused variable 'status' [-Werror=unused-variable]
> 
> Remove the variable again.
> 
> Fixes: c4e521b654e1 ("scsi: qla2xxx: Split the __qla2x00_abort_all_cmds() function")
> Fixes: f2ffd4e5bc7b ("scsi: qla2xxx: Timeouts occur on surprise removal of QLogic adapter")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> Maybe check carefully that the merge in linux-next is otherwise correct
> ---
>  drivers/scsi/qla2xxx/qla_os.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/scsi/qla2xxx/qla_os.c b/drivers/scsi/qla2xxx/qla_os.c
> index 63c47bc7ae59..db331cb5ba3c 100644
> --- a/drivers/scsi/qla2xxx/qla_os.c
> +++ b/drivers/scsi/qla2xxx/qla_os.c
> @@ -1788,7 +1788,7 @@ static void qla2x00_abort_srb(struct qla_qpair *qp, srb_t *sp, const int res,
>  static void
>  __qla2x00_abort_all_cmds(struct qla_qpair *qp, int res)
>  {
> -	int cnt, status;
> +	int cnt;
>  	unsigned long flags;
>  	srb_t *sp;
>  	scsi_qla_host_t *vha = qp->vha;

When I prepared commit c4e521b654e1 I verified that my patch did not produce any
warnings when building with W=1. So something must be wrong at your side. Did you
perhaps start from linux-next to prepare this patch? If so, please submit this
patch to Stephen Rothwell.

Bart.

  reply	other threads:[~2018-12-10 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 20:51 [PATCH] scsi: qla2xxx: fix unused function warning Arnd Bergmann
2018-12-10 21:01 ` Bart Van Assche [this message]
2018-12-10 21:28   ` Arnd Bergmann
2018-12-10 21:31     ` James Bottomley

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=1544475666.185366.378.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=William.Kuzeja@stratus.com \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=darren.trapp@cavium.com \
    --cc=hare@suse.de \
    --cc=himanshu.madhani@cavium.com \
    --cc=hmadhani@marvell.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=loberman@redhat.com \
    --cc=martin.petersen@oracle.com \
    --cc=qla2xxx-upstream@qlogic.com \
    --cc=quinn.tran@cavium.com \
    --cc=sfr@canb.auug.org.au \
    /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