linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.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>,
	Gwendal Grignou <gwendal@chromium.org>
Subject: Re: linux-next: build warning after merge of the mfd tree
Date: Tue, 5 Jun 2018 07:55:13 +0100	[thread overview]
Message-ID: <20180605065513.GD21163@dell> (raw)
In-Reply-To: <20180605131507.3f217038@canb.auug.org.au>

On Tue, 05 Jun 2018, Stephen Rothwell wrote:

> Hi Lee,
> 
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
> 
> drivers/mfd/cros_ec_dev.c:265:13: warning: '__remove' defined but not used [-Wunused-function]
>  static void __remove(struct device *dev) { }
>              ^~~~~~~~
> 
> Introduced by commit
> 
>   3aa2177e4787 ("mfd: cros_ec: Use devm_kzalloc for private data")

Thanks Stephen.  Will chase today.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2018-06-05  6:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05  3:15 linux-next: build warning after merge of the mfd tree Stephen Rothwell
2018-06-05  6:55 ` Lee Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-07  2:44 Stephen Rothwell
     [not found] <20190627151140.232a87e2@canb.auug.org.au>
2019-06-27  5:59 ` Keerthy
2019-07-02  8:49   ` Stephen Rothwell
2019-07-02 11:09     ` Lee Jones
2017-11-30  0:35 Stephen Rothwell
2017-11-30  8:28 ` Lee Jones
2017-01-25  4:54 Stephen Rothwell
2017-01-25  8:13 ` Benjamin Gaignard
2013-07-03  5:56 Stephen Rothwell
2013-07-07 18:29 ` Sebastian Andrzej Siewior
2011-12-20  3:11 Stephen Rothwell
2010-11-29  0:52 Stephen Rothwell
2010-11-30 10:02 ` Samuel Ortiz
2010-03-03  5:22 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=20180605065513.GD21163@dell \
    --to=lee.jones@linaro.org \
    --cc=gwendal@chromium.org \
    --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).