linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Russell King <linux@armlinux.org.uk>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	linux-pm@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v2] clk: Provide notifier stubs when !COMMON_CLK
Date: Tue, 28 Jun 2016 21:01:00 +0200	[thread overview]
Message-ID: <20160628190100.GA11586@kozik-lap> (raw)
In-Reply-To: <20160628172653.GB1521@codeaurora.org>

On Tue, Jun 28, 2016 at 10:26:53AM -0700, Stephen Boyd wrote:
> On 06/28, Krzysztof Kozlowski wrote:
> > The clk notifier symbols are hidden by COMMON_CLK.  However on some
> > platforms HAVE_CLK might be set while COMMON_CLK not which leads to
> > compile test build errors like:
> > 
> > $ make.cross ARCH=sh
> >    drivers/devfreq/tegra-devfreq.c: In function 'tegra_actmon_rate_notify_cb':
> > >> drivers/devfreq/tegra-devfreq.c:391:16: error: 'POST_RATE_CHANGE' undeclared (first use in this function)
> >      if (action != POST_RATE_CHANGE)
> >                    ^
> >    drivers/devfreq/tegra-devfreq.c: In function 'tegra_devfreq_probe':
> > >> drivers/devfreq/tegra-devfreq.c:654:8: error: implicit declaration of function 'clk_notifier_register' [-Werror=implicit-function-declaration]
> >      err = clk_notifier_register(tegra->emc_clock, &tegra->rate_change_nb);
> >            ^
> > 
> > Export the macros and data type declarations outside of COMMON_CLK ifdef
> > and provide stubs to fix the compile testing.
> > 
> > Reported-by: kbuild test robot <lkp@intel.com>
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> > 
> > ---
> > 
> 
> Ok. Did you want some stable branch to pull this in and base your
> use case on?

It is only one patch but indeed without the branch my patches would have
to wait for next release. If you would be so kind, could you prepare
the stable branch? I hope MyungJoo Ham will use it.

Anyway I encountered more linkage errors for clk API (like clk_get_rate()).
They happen for various compile-tested drivers in case of MIPS (and
maybe others like SH). I will investigate it more but I think it is not
related strictly to this issue.

Best regards,
Krzysztof

  reply	other threads:[~2016-06-28 19:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 11:25 [PATCH v2] clk: Provide notifier stubs when !COMMON_CLK Krzysztof Kozlowski
2016-06-28 11:58 ` Bartlomiej Zolnierkiewicz
2016-06-28 17:26 ` Stephen Boyd
2016-06-28 19:01   ` Krzysztof Kozlowski [this message]
2016-06-29  0:14     ` Stephen Boyd

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=20160628190100.GA11586@kozik-lap \
    --to=k.kozlowski@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mturquette@baylibre.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=sboyd@codeaurora.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 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).