linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the scsi-fixes tree
Date: Tue, 28 Apr 2020 17:27:57 -0700	[thread overview]
Message-ID: <ba29c840-e327-6f0b-b760-188aec566c6c@linux.ibm.com> (raw)
In-Reply-To: <20200429092154.35958687@canb.auug.org.au>

On 4/28/20 4:21 PM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the scsi-fixes tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
> 
> drivers/scsi/ibmvscsi/ibmvscsi.c: In function 'ibmvscsi_remove':
> drivers/scsi/ibmvscsi/ibmvscsi.c:2323:16: warning: unused variable 'flags' [-Wunused-variable]
>  2323 |  unsigned long flags;
>       |                ^~~~~
> 
> Introduced by commit
> 
>   5b77d181bee1 ("scsi: ibmvscsi: Fix WARN_ON during event pool release")
> 

Crud, artifact from removing the spinlock.

Martin,

Do you want me to resend, or can you fixup your tree?

-Tyrel

  reply	other threads:[~2020-04-29  0:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 23:21 linux-next: build warning after merge of the scsi-fixes tree Stephen Rothwell
2020-04-29  0:27 ` Tyrel Datwyler [this message]
2020-04-29  3:00   ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2021-01-10 21:31 Stephen Rothwell
2021-01-10 22:14 ` Stephen Rothwell
2018-06-13 22:13 Stephen Rothwell

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=ba29c840-e327-6f0b-b760-188aec566c6c@linux.ibm.com \
    --to=tyreld@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).