linux-kernel - Re: linux-next: build failure after merge of the pm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 9 Dec 2015 07:30:31 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ashwin Chaugule <ashwin.chaugule@...aro.org>
Subject: Re: linux-next: build failure after merge of the pm tree

On 09-12-15, 12:54, Stephen Rothwell wrote:
> Hi Rafael,
> 
> After merging the pm tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> ERROR: "gov_cancel_work" [drivers/cpufreq/cpufreq_ondemand.ko] undefined!
> 
> Caused by commit
> 
>   68e115b19a01 ("cpufreq: governor: replace per-cpu delayed work with timers")
> 
> I have used the pm tree from next-20151208 for today.

Yeah, it missed this stupid change. Sorry about that.

diff --git a/drivers/cpufreq/cpufreq_governor.c b/drivers/cpufreq/cpufreq_governor.c
index 948771f169d2..4de12fd35b1f 100644
--- a/drivers/cpufreq/cpufreq_governor.c
+++ b/drivers/cpufreq/cpufreq_governor.c
@@ -205,6 +205,7 @@ void gov_cancel_work(struct cpu_common_dbs_info *shared)
        gov_cancel_timers(shared->policy);
        atomic_set(&shared->skip_work, 0);
 }
+EXPORT_SYMBOL_GPL(gov_cancel_work);
 
 /* Will return if we need to evaluate cpu load again or not */
 static bool need_load_eval(struct cpu_common_dbs_info *shared,


Rafael, I am resending the original patch with this change.

-- 
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/