All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@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>,
	Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>,
	Hien Dang <hien.dang.eb@rvc.renesas.com>,
	Yoshihiro Kaneko <ykaneko0929@gmail.com>
Subject: Re: linux-next: build warning after merge of the libata tree
Date: Tue, 13 Feb 2018 06:42:07 -0800	[thread overview]
Message-ID: <20180213144207.GO695913@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180213140449.35e337cb@canb.auug.org.au>

On Tue, Feb 13, 2018 at 02:04:49PM +1100, Stephen Rothwell wrote:
> Hi Tejun,
> 
> After merging the libata tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/ata/sata_rcar.c: In function 'sata_rcar_init_controller':
> drivers/ata/sata_rcar.c:821:16: warning: unused variable 'base' [-Wunused-variable]
>   void __iomem *base = priv->base;
>                 ^~~~
> 
> Introduced by commit
> 
>   da77d76b95a0 ("sata_rcar: Reset SATA PHY when Salvator-X board resumes")

Just applied Geert's patch to remove the warning.

Thanks.

-- 
tejun

  reply	other threads:[~2018-02-13 14:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13  3:04 linux-next: build warning after merge of the libata tree Stephen Rothwell
2018-02-13 14:42 ` Tejun Heo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-19  2:40 Stephen Rothwell
2022-09-19  8:01 ` Damien Le Moal
2022-09-19 23:56 ` Damien Le Moal
2022-09-20 19:25   ` Serge Semin
2022-06-20  0:34 Stephen Rothwell
2022-06-20  0:43 ` Damien Le Moal
2022-06-20  8:21 ` Stephen Rothwell
2022-06-20  8:53   ` Damien Le Moal
2022-06-20 10:57     ` Sergey Shtylyov
2022-06-20 11:07       ` Damien Le Moal
2022-06-20 20:07         ` Sergey Shtylyov
2022-06-20 20:08         ` Sergey Shtylyov
2018-03-20  4:57 Stephen Rothwell
2018-03-20  4:59 ` Richard Zhu
2018-01-18  4:26 Stephen Rothwell
2017-06-28  5:51 Stephen Rothwell
2017-06-28 18:28 ` Tejun Heo
2012-02-13  5:27 Stephen Rothwell
2012-02-24  3:08 ` Stephen Rothwell
2012-02-24  4:06   ` Jeff Garzik
2012-02-24  4:14     ` Stephen Rothwell
2012-02-24 12:22       ` Stephen Rothwell
2012-02-24 17:01         ` Jeff Garzik

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=20180213144207.GO695913@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=hien.dang.eb@rvc.renesas.com \
    --cc=khiem.nguyen.xt@rvc.renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=ykaneko0929@gmail.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.