linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Dmitry Osipenko <digetx@gmail.com>,
	linux-pm@vger.kernel.org, "Enrico Weigelt,
	metux IT consult" <lkml@metux.net>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH] PM / devfreq: tegra30: add COMMON_CLK dependency
Date: 13 Dec 2019 14:09:55 +0900	[thread overview]
Message-ID: <87sglo4xr0.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <23cc9bbb-f6a4-fc1c-7678-79040d3a18aa@samsung.com>


Hi Chanwoo

> > Compile-testing the new driver on platforms without CONFIG_COMMON_CLK
> > leads to a link error:
> > 
> > 	drivers/devfreq/tegra30-devfreq.o: In function `tegra_devfreq_target':
> > 	tegra30-devfreq.c:(.text+0x288): undefined reference to `clk_set_min_rate'
> > 
> > Add a dependency on COMMON_CLK to avoid this.
> > 
> > Fixes: 35f8dbc727212 ("PM / devfreq: tegra: Enable COMPILE_TEST for the driver")
> > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > ---
(snip)
> Thanks for the fixup.
> 
> But, it was merged as following:
> - https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git/commit/?h=devfreq-next&id=252ef98ed524612667e2e2a0ce065fe21e80ec93

Thanks, nice to know !!


Thank you for your help !!
Best regards
---
Kuninori Morimoto

  reply	other threads:[~2019-12-13  5:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191213044804epcas1p34eaf8872b5688c01255931c79bfd0ef0@epcas1p3.samsung.com>
2019-12-13  4:47 ` [PATCH] PM / devfreq: tegra30: add COMMON_CLK dependency Kuninori Morimoto
2019-12-13  4:57   ` Chanwoo Choi
2019-12-13  5:09     ` Kuninori Morimoto [this message]
2019-12-17  5:12       ` Kuninori Morimoto

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=87sglo4xr0.wl-kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=arnd@arndb.de \
    --cc=cw00.choi@samsung.com \
    --cc=digetx@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkml@metux.net \
    --cc=mturquette@baylibre.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=sboyd@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 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).