Linux-Next discussions
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: linux-next: build warning after merge of the soundwire tree
Date: Thu, 22 Aug 2019 11:55:12 +0530	[thread overview]
Message-ID: <20190822062512.GL12733@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20190822160425.6998054e@canb.auug.org.au>

On 22-08-19, 16:04, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the soundwire tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
> 
> drivers/soundwire/intel.c: In function 'sdw_master_read_intel_prop':
> drivers/soundwire/intel.c:829:12: warning: unused variable 'i' [-Wunused-variable]
>   int nval, i;
>             ^
> drivers/soundwire/intel.c:829:6: warning: unused variable 'nval' [-Wunused-variable]
>   int nval, i;
>       ^~~~
> 
> Introduced by commit
> 
>   085f4ace103d ("soundwire: intel: read mclk_freq property from firmware")

Thanks Stephen for the report. I have fixed it up by removing these.
Posting the patch now

Thanks
-- 
~Vinod

  reply	other threads:[~2019-08-22  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22  6:04 linux-next: build warning after merge of the soundwire tree Stephen Rothwell
2019-08-22  6:25 ` Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-29  8:14 Stephen Rothwell
2020-05-02 11:39 ` Vinod Koul

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=20190822062512.GL12733@vkoul-mobl.Dlink \
    --to=vkoul@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.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