From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Dave Jones <davej@redhat.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
박경민 <kyungmin.park@samsung.com>,
"RafaelJ.Wysocki<rjw"@sisk.pl, linux-pm@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the cpufreq tree
Date: Mon, 05 Mar 2012 01:46:07 +0000 (GMT) [thread overview]
Message-ID: <13197479.540821330911965933.JavaMail.weblogic@epv6ml06> (raw)
Hello,
The patch "CPUfreq ondemand: handle QoS request on DVFS response latency" that introduced the mentioned errors requires the patch "PM / QoS: Introduce new classes: DMA-Throughput and DVFS-Latency" get merged, too. I guess that patch will be at pm-qos tree if get merged (v2 patch has been released 7 days ago).
Cheers!
MyungJoo.
------- Original Message -------
Sender : Stephen Rothwell<sfr@canb.auug.org.au>
Date : 2012-03-01 11:56 (GMT+09:00)
Title : linux-next: build failure after merge of the cpufreq tree
Hi Dave,
After merging the cpufreq tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/cpufreq/cpufreq_ondemand.c: In function 'cpufreq_gov_dbs_init':
drivers/cpufreq/cpufreq_ondemand.c:880:28: error: 'PM_QOS_DVFS_RESPONSE_LATENCY' undeclared (first use in this function)
drivers/cpufreq/cpufreq_ondemand.c: In function 'cpufreq_gov_dbs_exit':
drivers/cpufreq/cpufreq_ondemand.c:896:25: error: 'PM_QOS_DVFS_RESPONSE_LATENCY' undeclared (first use in this function)
Caused by commit 500e8ca39c56 ("[CPUFREQ] ondemand: handle QoS request on
DVFS response latency").
I have used the cpufreq tree fomr next-20120229 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
--
MyungJoo Ham (함명주), PHD
System S/W Lab, S/W Platform Team, Software Center
Samsung Electronics
Cell: +82-10-6714-2858
WARNING: multiple messages have this Message-ID (diff)
From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Dave Jones <davej@redhat.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
박경민 <kyungmin.park@samsung.com>,
"RafaelJ.Wysocki<rjw"@sisk.pl, linux-pm@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the cpufreq tree
Date: Mon, 05 Mar 2012 01:46:07 +0000 (GMT) [thread overview]
Message-ID: <13197479.540821330911965933.JavaMail.weblogic@epv6ml06> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1567 bytes --]
Hello,
The patch "CPUfreq ondemand: handle QoS request on DVFS response latency" that introduced the mentioned errors requires the patch "PM / QoS: Introduce new classes: DMA-Throughput and DVFS-Latency" get merged, too. I guess that patch will be at pm-qos tree if get merged (v2 patch has been released 7 days ago).
Cheers!
MyungJoo.
------- Original Message -------
Sender : Stephen Rothwell<sfr@canb.auug.org.au>
Date : 2012-03-01 11:56 (GMT+09:00)
Title : linux-next: build failure after merge of the cpufreq tree
Hi Dave,
After merging the cpufreq tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/cpufreq/cpufreq_ondemand.c: In function 'cpufreq_gov_dbs_init':
drivers/cpufreq/cpufreq_ondemand.c:880:28: error: 'PM_QOS_DVFS_RESPONSE_LATENCY' undeclared (first use in this function)
drivers/cpufreq/cpufreq_ondemand.c: In function 'cpufreq_gov_dbs_exit':
drivers/cpufreq/cpufreq_ondemand.c:896:25: error: 'PM_QOS_DVFS_RESPONSE_LATENCY' undeclared (first use in this function)
Caused by commit 500e8ca39c56 ("[CPUFREQ] ondemand: handle QoS request on
DVFS response latency").
I have used the cpufreq tree fomr next-20120229 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
--
MyungJoo Ham (ÇÔ¸íÁÖ), PHD
System S/W Lab, S/W Platform Team, Software Center
Samsung Electronics
Cell: +82-10-6714-2858ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2012-03-05 1:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 1:46 MyungJoo Ham [this message]
2012-03-05 1:46 ` linux-next: build failure after merge of the cpufreq tree MyungJoo Ham
2012-03-07 5:02 ` [PATCH v3] PM / QoS: Introduce new classes: DMA-Throughput and DVFS-Latency MyungJoo Ham
2012-03-07 9:02 ` Rafael J. Wysocki
2012-03-07 9:36 ` MyungJoo Ham
2012-03-09 8:17 ` MyungJoo Ham
2012-03-10 22:22 ` Rafael J. Wysocki
2012-03-08 3:47 ` mark gross
2012-03-09 5:53 ` MyungJoo Ham
2012-03-10 22:53 ` Rafael J. Wysocki
2012-03-16 8:30 ` MyungJoo Ham
2012-03-17 0:01 ` Rafael J. Wysocki
2012-03-18 17:06 ` mark gross
2012-03-26 12:06 ` MyungJoo Ham
2012-03-26 14:38 ` mark gross
2012-03-18 16:50 ` mark gross
2012-03-10 22:25 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2012-03-01 2:56 linux-next: build failure after merge of the cpufreq tree Stephen Rothwell
2012-03-01 3:01 ` Dave Jones
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=13197479.540821330911965933.JavaMail.weblogic@epv6ml06 \
--to=myungjoo.ham@samsung.com \
--cc="RafaelJ.Wysocki<rjw"@sisk.pl \
--cc=davej@redhat.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.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.