From: Stephen Boyd <sboyd@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mike Turquette <mturquette@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the clk tree
Date: Tue, 5 May 2015 21:41:26 -0700 [thread overview]
Message-ID: <20150506044126.GA2817@codeaurora.org> (raw)
In-Reply-To: <20150506140543.426ed29b@canb.auug.org.au>
On 05/06, Stephen Rothwell wrote:
> Hi all,
>
> After merging the clk tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/clk/clk.c:2231:13: warning: 'clk_is_orphan' defined but not used [-Wunused-function]
> static bool clk_is_orphan(const struct clk *clk)
> ^
>
> Introduced by commit ece3ffbe1b7b ("clk: prevent orphan clocks from
> being used").
>
> CONFIG_OF is not set for this build ...
Thanks for the report. kbuild robot also reported this problem
the other day. We came up with a way to not have this function at
all though so this problem should go away tomorrow.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-05-06 4:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 4:05 linux-next: build warning after merge of the clk tree Stephen Rothwell
2015-05-06 4:41 ` Stephen Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-11 21:39 Stephen Rothwell
2016-12-12 8:05 ` Boris Brezillon
2016-12-12 8:19 ` Stephen Rothwell
2018-10-17 21:51 Stephen Rothwell
2018-10-18 18:21 ` Stephen Boyd
2019-04-30 0:19 Stephen Rothwell
2019-04-30 1:44 ` Anson Huang
2019-04-30 5:56 ` Stephen Rothwell
2019-08-15 23:57 Stephen Rothwell
2019-08-16 18:10 ` Stephen Boyd
2020-06-29 23:53 Stephen Rothwell
2020-06-30 8:11 ` Maxime Ripard
2020-07-08 11:10 ` Stephen Rothwell
2020-07-16 0:25 ` Stephen Boyd
2024-09-09 1:27 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=20150506044126.GA2817@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@linaro.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 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.