All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: linux-next: build warning after merge of the libata tree
Date: Thu, 18 Jan 2018 15:26:01 +1100	[thread overview]
Message-ID: <20180118152601.31761830@canb.auug.org.au> (raw)

Hi Tejun,

After merging the libata tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

drivers/phy/broadcom/phy-brcm-sata.c: In function 'brcm_stb_sata_calibrate':
drivers/phy/broadcom/phy-brcm-sata.c:514:24: warning: unused variable 'priv' [-Wunused-variable]
  struct brcm_sata_phy *priv = port->phy_priv;
                        ^~~~

Introduced by commit

  3e507769d15e ("phy: brcm-sata: Implement calibrate callback")

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2018-01-18  4:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  4:26 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-19  2:40 linux-next: build warning after merge of the libata tree 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-02-13  3:04 Stephen Rothwell
2018-02-13 14:42 ` Tejun Heo
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=20180118152601.31761830@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tj@kernel.org \
    /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.