From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Ming Lei <ming.lei@canonical.com>
Subject: Re: linux-next: build warning after merge of the final tree (driver-core tree related)
Date: Wed, 19 Jun 2013 07:38:14 -0700 [thread overview]
Message-ID: <20130619143814.GB8413@kroah.com> (raw)
In-Reply-To: <20130619180027.ede041e59b1c642c7e5c603c@canb.auug.org.au>
On Wed, Jun 19, 2013 at 06:00:27PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig among others) produced these warnings:
>
> drivers/base/firmware_class.c:1254:12: warning: 'cache_firmware' defined but not used [-Wunused-function]
> static int cache_firmware(const char *fw_name)
> ^
> drivers/base/firmware_class.c:1281:12: warning: 'uncache_firmware' defined but not used [-Wunused-function]
> static int uncache_firmware(const char *fw_name)
> ^
>
> Revealed by commit 93232e46b209 ("firmware loader: don't export
> cache_firmware and uncache_firmware") from the driver-core tree. These
> are only used if CONFIG_PM_SLEEP is set.
Odd. Ming, can you send me a patch for this?
thanks,
greg k-h
next prev parent reply other threads:[~2013-06-19 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 8:00 linux-next: build warning after merge of the final tree (driver-core tree related) Stephen Rothwell
2013-06-19 14:38 ` Greg KH [this message]
2013-06-20 1:34 ` Ming Lei
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 7:32 Stephen Rothwell
2013-06-06 7:59 ` Ming Lei
2010-09-07 1:54 Stephen Rothwell
2010-09-07 2:34 ` Greg KH
2010-09-07 7:05 ` Stephen Rothwell
2010-09-13 15:51 ` Randy Dunlap
2010-09-13 19:26 ` Thomas Renninger
2010-09-13 20:57 ` Greg KH
2010-09-14 7:22 ` Thomas Renninger
2010-09-14 13:28 ` Greg KH
2010-09-14 4:31 ` Stephen Rothwell
2010-09-14 5:14 ` Randy Dunlap
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=20130619143814.GB8413@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ming.lei@canonical.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;
as well as URLs for NNTP newsgroup(s).