linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Chaotian Jing <chaotian.jing@mediatek.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 mmc tree
Date: Tue, 22 Oct 2019 09:31:12 +0200	[thread overview]
Message-ID: <CAPDyKFpUEXzcSN-eEDRNcRWWp8P-yveBirwerhrYh+WMdswnqg@mail.gmail.com> (raw)
In-Reply-To: <20191022114737.0fd6211c@canb.auug.org.au>

On Tue, 22 Oct 2019 at 02:47, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the mmc tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/mmc/core/block.c: In function '__mmc_blk_ioctl_cmd':
> drivers/mmc/core/block.c:500:6: warning: unused variable 'status' [-Wunused-variable]
>   500 |  u32 status = 0;
>       |      ^~~~~~
>
> Introduced by commit
>
>   05224f7e4975 ("mmc: block: Add CMD13 polling for MMC IOCTLS with R1B response")
>
> --
> Cheers,
> Stephen Rothwell

Thanks for the report. I have amended the patch to address the warning.

Kind regards
Uffe

  reply	other threads:[~2019-10-22  7:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  0:47 linux-next: build warning after merge of the mmc tree Stephen Rothwell
2019-10-22  7:31 ` Ulf Hansson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-25  3:20 Stephen Rothwell
2020-02-19 23:31 Stephen Rothwell
2020-02-20  1:38 ` Baolin Wang
2019-03-19  1:15 Stephen Rothwell
2017-11-02  1:36 Stephen Rothwell
2017-11-02  1:47 ` Doug Anderson
2017-11-02 15:03   ` Ulf Hansson

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=CAPDyKFpUEXzcSN-eEDRNcRWWp8P-yveBirwerhrYh+WMdswnqg@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=chaotian.jing@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).