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

On Tue, Feb 09, 2021 at 03:32:38PM +0100, Rafael J. Wysocki wrote: > On Mon, Feb 8, 2021 at 8:48 PM Andy Shevchenko > wrote: > > On Mon, Feb 8, 2021 at 9:47 PM Andy Shevchenko > > wrote: > > > On Mon, Feb 8, 2021 at 9:30 PM Rafael J. Wysocki > > > wrote: > > > > On Friday, February 5, 2021

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

On Mon, Feb 8, 2021 at 8:48 PM Andy Shevchenko wrote: > > On Mon, Feb 8, 2021 at 9:47 PM Andy Shevchenko > wrote: > > On Mon, Feb 8, 2021 at 9:30 PM Rafael J. Wysocki wrote: > > > > > > On Friday, February 5, 2021 12:15:22 PM CET Andy Shevchenko wrote: > > > > On Fri, Feb 5, 2021 at 11:14 AM

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

On Mon, Feb 8, 2021 at 9:47 PM Andy Shevchenko wrote: > On Mon, Feb 8, 2021 at 9:30 PM Rafael J. Wysocki wrote: > > > > On Friday, February 5, 2021 12:15:22 PM CET Andy Shevchenko wrote: > > > On Fri, Feb 5, 2021 at 11:14 AM Andy Shevchenko > > > wrote: > > > > On Friday, February 5, 2021,

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

On Mon, Feb 8, 2021 at 9:30 PM Rafael J. Wysocki wrote: > > On Friday, February 5, 2021 12:15:22 PM CET Andy Shevchenko wrote: > > On Fri, Feb 5, 2021 at 11:14 AM Andy Shevchenko > > wrote: > > > On Friday, February 5, 2021, Stephen Rothwell > > > wrote: > > > > >> After merging the pm tree,

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

On Friday, February 5, 2021 12:15:22 PM CET Andy Shevchenko wrote: > On Fri, Feb 5, 2021 at 11:14 AM Andy Shevchenko > wrote: > > On Friday, February 5, 2021, Stephen Rothwell wrote: > > >> After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > >> failed like this: > >> > >

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

On Fri, Feb 5, 2021 at 11:14 AM Andy Shevchenko wrote: > On Friday, February 5, 2021, Stephen Rothwell wrote: >> After merging the pm tree, today's linux-next build (x86_64 allmodconfig) >> failed like this: >> > > Rafael, maybe I was unclear when explaining to you the dependencies with the >

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

Hi all, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/gma500/tc35876x-dsi-lvds.c: In function 'tc35876x_brightness_init': drivers/gpu/drm/gma500/tc35876x-dsi-lvds.c:454:8: error: implicit declaration of function

Re: [External] linux-next: build failure after merge of the pm tree

On Wed, 9 Dec 2020 10:04:22 -0500 Mark Pearson wrote: > On 09/12/2020 09:33, Jonathan Corbet wrote: > > On Wed, 9 Dec 2020 08:56:31 -0500 Mark Pearson > > wrote: > > > >> I do see: WARNING: document isn't included in any toctree but I > >> think this is benign - I believe I'm getting it just

Re: [External] linux-next: build failure after merge of the pm tree

Hi Jon, On 09/12/2020 09:33, Jonathan Corbet wrote: > On Wed, 9 Dec 2020 08:56:31 -0500 Mark Pearson > wrote: > >> I do see: WARNING: document isn't included in any toctree but I >> think this is benign - I believe I'm getting it just because I >> converted the file to .rst (as requested by

Re: [External] linux-next: build failure after merge of the pm tree

On Wed, 9 Dec 2020 08:56:31 -0500 Mark Pearson wrote: > I do see: >WARNING: document isn't included in any toctree > but I think this is benign - I believe I'm getting it just because I > converted the file to .rst (as requested by Andy Shevchenko). If this is > important and needs to be

Re: [External] linux-next: build failure after merge of the pm tree

On 09/12/2020 04:57, Stephen Rothwell wrote: > Hi all, > > After merging the pm tree, today's linux-next build (htmldocs) failed > like this: > > Sphinx parallel build error: > docutils.utils.SystemMessage: > /home/sfr/next/next/Documentation/ABI/testing/sysfs-platform_profile.rst:1: >

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

Hi all, After merging the pm tree, today's linux-next build (htmldocs) failed like this: Sphinx parallel build error: docutils.utils.SystemMessage: /home/sfr/next/next/Documentation/ABI/testing/sysfs-platform_profile.rst:1: (SEVERE/4) Missing matching underline for section title overline.

Re: linux-next: build failure after merge of the pm tree (Was: linux-next: build warning after merge of the pm tree)

On Wed, Oct 16, 2019 at 11:15:44AM +0200, Geert Uytterhoeven wrote: > On Tue, Oct 15, 2019 at 1:27 PM Rafael J. Wysocki wrote: > > On Tuesday, October 15, 2019 1:16:50 AM CEST Stephen Rothwell wrote: > > > On Tue, 15 Oct 2019 10:08:55 +1100 Stephen Rothwell > > > = > > > wrote: > > > This

Re: linux-next: build failure after merge of the pm tree (Was: linux-next: build warning after merge of the pm tree)

Hi Rafael, On Tue, Oct 15, 2019 at 1:27 PM Rafael J. Wysocki wrote: > On Tuesday, October 15, 2019 1:16:50 AM CEST Stephen Rothwell wrote: > > On Tue, 15 Oct 2019 10:08:55 +1100 Stephen Rothwell > > = > > wrote: > > > > > > After merging the pm tree, today's linux-next build (arm > > >

Re: linux-next: build failure after merge of the pm tree (Was: linux-next: build warning after merge of the pm tree)

On Tuesday, October 15, 2019 1:16:50 AM CEST Stephen Rothwell wrote: > > --Sig_/6GS1h5au_w04qPbsgg/ztsa > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: quoted-printable > > Hi all, > > On Tue, 15 Oct 2019 10:08:55 +1100 Stephen Rothwell = > wrote: > > > > After

linux-next: build failure after merge of the pm tree (Was: linux-next: build warning after merge of the pm tree)

Hi all, On Tue, 15 Oct 2019 10:08:55 +1100 Stephen Rothwell wrote: > > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > In file included from include/linux/irqchip.h:14, > from arch/arm/kernel/irq.c:26: >

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

On Wednesday, July 31, 2019 7:34:19 AM CEST Stephen Rothwell wrote: > > --Sig_/RVaztRR.13XAL2aXFk8lo/g > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: quoted-printable > > Hi all, > > After merging the pm tree, today's linux-next build (x86_64 allnoconfig) > failed

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

Hi all, After merging the pm tree, today's linux-next build (x86_64 allnoconfig) failed like this: x86_64-linux-gnu-ld: kernel/sched/core.o: in function `cpuidle_poll_time': core.c:(.text+0x230): multiple definition of `cpuidle_poll_time'; arch/x86/kernel/process.o:process.c:(.text+0xc0): first

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

Hi Stephen, On Monday, July 15, 2019 2:02:36 AM CEST Stephen Rothwell wrote: > > --Sig_/JvAwh/r3+t+V+F.+O2706e. > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: quoted-printable > > Hi all, > > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) >

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

Hi all, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from : include/linux/intel_rapl.h:116:19: error: field 'pcap_rapl_online' has incomplete type enum cpuhp_state pcap_rapl_online; ^~~~ Caused by

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

On Thursday, July 4, 2019 11:48:34 AM CEST Viresh Kumar wrote: > On 04-07-19, 19:41, Stephen Rothwell wrote: > > Hi all, > > > > After merging the pm tree, today's linux-next build (x86_64 allnoconfig) > > failed like this: > > > > In file included from kernel/power/qos.c:33: > >

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

On 04-07-19, 19:41, Stephen Rothwell wrote: > Hi all, > > After merging the pm tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > In file included from kernel/power/qos.c:33: > include/linux/pm_qos.h: In function 'dev_pm_qos_read_value': > include/linux/pm_qos.h:205:9:

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

Hi all, After merging the pm tree, today's linux-next build (x86_64 allnoconfig) failed like this: In file included from kernel/power/qos.c:33: include/linux/pm_qos.h: In function 'dev_pm_qos_read_value': include/linux/pm_qos.h:205:9: error: expected '(' before 'type' switch type {

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

On 01-07-19, 13:37, Stephen Rothwell wrote: > In file included from drivers/cpufreq/intel_pstate.c:11: > drivers/cpufreq/intel_pstate.c: In function 'intel_pstate_update_max_freq': > drivers/cpufreq/intel_pstate.c:912:31: error: 'struct cpufreq_policy' has no > member named 'user_policy'; did you

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

Hi all, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/cpufreq/intel_pstate.c:11: drivers/cpufreq/intel_pstate.c: In function 'intel_pstate_update_max_freq': drivers/cpufreq/intel_pstate.c:912:31: error: 'struct

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

Hi Rafael, After merging the pm tree, today's linux-next build (arm64 defconfig) failed like this: drivers/acpi/ec.o: In function `acpi_ec_dispatch_gpe': /home/broonie/next/next/drivers/acpi/ec.c:1040: undefined reference to `acpi_dispatch_gpe'

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

Hi Rafael, After merging the pm tree, today's linux-next build (arm64 defconfig) failed like this: drivers/acpi/ec.o: In function `acpi_ec_dispatch_gpe': /home/broonie/next/next/drivers/acpi/ec.c:1040: undefined reference to `acpi_dispatch_gpe'

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

On Mon, Sep 19, 2016 at 07:37:24AM +, MyungJoo Ham wrote: > > On Wednesday, September 14, 2016 02:27:47 PM Stephen Rothwell wrote: > > > Hi Rafael, > > > > > > After merging the pm tree, today's linux-next build (powerpc allyesconfig) > > > failed like this: > > > > > >

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

On Mon, Sep 19, 2016 at 07:37:24AM +, MyungJoo Ham wrote: > > On Wednesday, September 14, 2016 02:27:47 PM Stephen Rothwell wrote: > > > Hi Rafael, > > > > > > After merging the pm tree, today's linux-next build (powerpc allyesconfig) > > > failed like this: > > > > > >

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

> On Wednesday, September 14, 2016 02:27:47 PM Stephen Rothwell wrote: > > Hi Rafael, > > > > After merging the pm tree, today's linux-next build (powerpc allyesconfig) > > failed like this: > > > > drivers/devfreq/tegra-devfreq.c: In function 'tegra_devfreq_target': > >

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

> On Wednesday, September 14, 2016 02:27:47 PM Stephen Rothwell wrote: > > Hi Rafael, > > > > After merging the pm tree, today's linux-next build (powerpc allyesconfig) > > failed like this: > > > > drivers/devfreq/tegra-devfreq.c: In function 'tegra_devfreq_target': > >

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

On Wednesday, September 14, 2016 02:27:47 PM Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (powerpc allyesconfig) > failed like this: > > drivers/devfreq/tegra-devfreq.c: In function 'tegra_devfreq_target': > drivers/devfreq/tegra-devfreq.c:500:2:

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

On Wednesday, September 14, 2016 02:27:47 PM Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (powerpc allyesconfig) > failed like this: > > drivers/devfreq/tegra-devfreq.c: In function 'tegra_devfreq_target': > drivers/devfreq/tegra-devfreq.c:500:2:

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

Hi Rafael, After merging the pm tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/devfreq/tegra-devfreq.c: In function 'tegra_devfreq_target': drivers/devfreq/tegra-devfreq.c:500:2: error: implicit declaration of function 'clk_set_min_rate'

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

Hi Rafael, After merging the pm tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/devfreq/tegra-devfreq.c: In function 'tegra_devfreq_target': drivers/devfreq/tegra-devfreq.c:500:2: error: implicit declaration of function 'clk_set_min_rate'

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

On Fri, Jul 22, 2016 at 02:08:35PM +0200, Rafael J. Wysocki wrote: On Thursday, July 21, 2016 07:26:28 PM Steve Muckle wrote: On Fri, Jul 22, 2016 at 11:56:20AM +1000, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) failed

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

On Fri, Jul 22, 2016 at 02:08:35PM +0200, Rafael J. Wysocki wrote: On Thursday, July 21, 2016 07:26:28 PM Steve Muckle wrote: On Fri, Jul 22, 2016 at 11:56:20AM +1000, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) failed

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

On Thursday, July 21, 2016 07:26:28 PM Steve Muckle wrote: > On Fri, Jul 22, 2016 at 11:56:20AM +1000, Stephen Rothwell wrote: > > Hi Rafael, > > > > After merging the pm tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > > ERROR: "cpufreq_driver_resolve_freq"

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

On Thursday, July 21, 2016 07:26:28 PM Steve Muckle wrote: > On Fri, Jul 22, 2016 at 11:56:20AM +1000, Stephen Rothwell wrote: > > Hi Rafael, > > > > After merging the pm tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > > ERROR: "cpufreq_driver_resolve_freq"

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

On Fri, Jul 22, 2016 at 11:56:20AM +1000, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > ERROR: "cpufreq_driver_resolve_freq" [kernel/sched/cpufreq_schedutil.ko] > undefined! > > Caused by commit >

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

On Fri, Jul 22, 2016 at 11:56:20AM +1000, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > ERROR: "cpufreq_driver_resolve_freq" [kernel/sched/cpufreq_schedutil.ko] > undefined! > > Caused by commit >

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

Hi Rafael, After merging the pm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: ERROR: "cpufreq_driver_resolve_freq" [kernel/sched/cpufreq_schedutil.ko] undefined! Caused by commit 5cbea46984d6 ("cpufreq: schedutil: map raw required frequency to driver frequency")

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

Hi Rafael, After merging the pm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: ERROR: "cpufreq_driver_resolve_freq" [kernel/sched/cpufreq_schedutil.ko] undefined! Caused by commit 5cbea46984d6 ("cpufreq: schedutil: map raw required frequency to driver frequency")

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

On Monday, July 11, 2016 03:29:55 PM Stephen Rothwell wrote: > Hi Mika, > > On Mon, 11 Jul 2016 07:48:17 +0300 Mika Westerberg > wrote: > > > > Looks like it is the module name (configfs.o) that confuses modpost or > > linker. The below patch fixes it for me. >

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

On Monday, July 11, 2016 03:29:55 PM Stephen Rothwell wrote: > Hi Mika, > > On Mon, 11 Jul 2016 07:48:17 +0300 Mika Westerberg > wrote: > > > > Looks like it is the module name (configfs.o) that confuses modpost or > > linker. The below patch fixes it for me. > > That makes sense. Thanks.

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

Hi Mika, On Mon, 11 Jul 2016 07:48:17 +0300 Mika Westerberg wrote: > > Looks like it is the module name (configfs.o) that confuses modpost or > linker. The below patch fixes it for me. That makes sense. Thanks. -- Cheers, Stephen Rothwell

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

Hi Mika, On Mon, 11 Jul 2016 07:48:17 +0300 Mika Westerberg wrote: > > Looks like it is the module name (configfs.o) that confuses modpost or > linker. The below patch fixes it for me. That makes sense. Thanks. -- Cheers, Stephen Rothwell

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

On Mon, Jul 11, 2016 at 11:46:53AM +1000, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > ERROR: "configfs_unregister_subsystem" [samples/configfs/configfs_sample.ko] > undefined! > ERROR:

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

On Mon, Jul 11, 2016 at 11:46:53AM +1000, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > ERROR: "configfs_unregister_subsystem" [samples/configfs/configfs_sample.ko] > undefined! > ERROR:

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "configfs_unregister_subsystem" [samples/configfs/configfs_sample.ko] undefined! ERROR: "configfs_register_subsystem" [samples/configfs/configfs_sample.ko] undefined! ERROR:

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "configfs_unregister_subsystem" [samples/configfs/configfs_sample.ko] undefined! ERROR: "configfs_register_subsystem" [samples/configfs/configfs_sample.ko] undefined! ERROR:

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

Hi Rafael, After merging the pm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/cell/cpufreq_spudemand.c: In function 'spu_gov_govern': arch/powerpc/platforms/cell/cpufreq_spudemand.c:98:7: error: 'CPUFREQ_GOV_START' undeclared (first use in

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

Hi Rafael, After merging the pm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/cell/cpufreq_spudemand.c: In function 'spu_gov_govern': arch/powerpc/platforms/cell/cpufreq_spudemand.c:98:7: error: 'CPUFREQ_GOV_START' undeclared (first use in

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

On Friday, April 01, 2016 12:27:43 PM Stephen Rothwell wrote: > Hi Rafael, Hi Stephen, > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > ERROR: "__tracepoint_cpu_frequency" [kernel/sched/cpufreq_schedutil.ko] > undefined! > > Caused by commit

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

On Friday, April 01, 2016 12:27:43 PM Stephen Rothwell wrote: > Hi Rafael, Hi Stephen, > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > ERROR: "__tracepoint_cpu_frequency" [kernel/sched/cpufreq_schedutil.ko] > undefined! > > Caused by commit

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "__tracepoint_cpu_frequency" [kernel/sched/cpufreq_schedutil.ko] undefined! Caused by commit d4913d2934b5 ("cpufreq: schedutil: New governor based on scheduler utilization data")

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "__tracepoint_cpu_frequency" [kernel/sched/cpufreq_schedutil.ko] undefined! Caused by commit d4913d2934b5 ("cpufreq: schedutil: New governor based on scheduler utilization data")

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:

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

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

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

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

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:

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

On Sunday, November 01, 2015 05:57:18 PM Stephen Rothwell wrote: > Hi Rafael, Hi, Thanks for the patch! > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > arch/arm/mach-mediatek/mediatek.c: In function 'mediatek_timer_init': >

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

Hi Rafael, After merging the pm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/mach-mediatek/mediatek.c: In function 'mediatek_timer_init': arch/arm/mach-mediatek/mediatek.c:43:2: error: implicit declaration of function 'clocksource_of_init'

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

Hi Rafael, After merging the pm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/mach-mediatek/mediatek.c: In function 'mediatek_timer_init': arch/arm/mach-mediatek/mediatek.c:43:2: error: implicit declaration of function 'clocksource_of_init'

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

On Sunday, November 01, 2015 05:57:18 PM Stephen Rothwell wrote: > Hi Rafael, Hi, Thanks for the patch! > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > arch/arm/mach-mediatek/mediatek.c: In function 'mediatek_timer_init': >

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

Hi Len, On Mon, 13 Apr 2015 14:24:42 +1000 Stephen Rothwell wrote: > > Hi Rafael, > > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > In file included from arch/x86/include/asm/msr.h:131:0, > from

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

Hi Len, On Mon, 13 Apr 2015 14:24:42 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from arch/x86/include/asm/msr.h:131:0, from

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

On Monday, April 13, 2015 02:24:42 PM Stephen Rothwell wrote: > > --Sig_/wQd_Ak5TvD_LSZFUNsW5WJr > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: quoted-printable > > Hi Rafael, > > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like

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

On Monday, April 13, 2015 02:24:42 PM Stephen Rothwell wrote: --Sig_/wQd_Ak5TvD_LSZFUNsW5WJr Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this:

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from arch/x86/include/asm/msr.h:131:0, from arch/x86/include/asm/processor.h:20, from arch/x86/include/asm/thread_info.h:23,

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from arch/x86/include/asm/msr.h:131:0, from arch/x86/include/asm/processor.h:20, from arch/x86/include/asm/thread_info.h:23,

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

On Mon, Feb 09, 2015 at 03:21:25PM +, Jiang Liu wrote: > On 2015/2/9 23:10, Rafael J. Wysocki wrote: > > On Monday, February 09, 2015 06:23:40 AM Lorenzo Pieralisi wrote: > >> On Mon, Feb 09, 2015 at 05:36:07AM +, Jiang Liu wrote: > >>> Hi Rafael and Lorenzo, > >>> With more closer

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

On 2015/2/9 23:10, Rafael J. Wysocki wrote: > On Monday, February 09, 2015 06:23:40 AM Lorenzo Pieralisi wrote: >> On Mon, Feb 09, 2015 at 05:36:07AM +, Jiang Liu wrote: >>> Hi Rafael and Lorenzo, >>> With more closer review, I suspect statement "kfree(bus_range)" >>> in commit

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

On Monday, February 09, 2015 06:23:40 AM Lorenzo Pieralisi wrote: > On Mon, Feb 09, 2015 at 05:36:07AM +, Jiang Liu wrote: > > Hi Rafael and Lorenzo, > > With more closer review, I suspect statement "kfree(bus_range)" > > in commit d2be00c0fb5a ("of/pci: Free resources on failure in > >

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

On 2015/2/9 23:10, Rafael J. Wysocki wrote: On Monday, February 09, 2015 06:23:40 AM Lorenzo Pieralisi wrote: On Mon, Feb 09, 2015 at 05:36:07AM +, Jiang Liu wrote: Hi Rafael and Lorenzo, With more closer review, I suspect statement kfree(bus_range) in commit d2be00c0fb5a (of/pci:

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

On Mon, Feb 09, 2015 at 03:21:25PM +, Jiang Liu wrote: On 2015/2/9 23:10, Rafael J. Wysocki wrote: On Monday, February 09, 2015 06:23:40 AM Lorenzo Pieralisi wrote: On Mon, Feb 09, 2015 at 05:36:07AM +, Jiang Liu wrote: Hi Rafael and Lorenzo, With more closer review, I suspect

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

On Monday, February 09, 2015 06:23:40 AM Lorenzo Pieralisi wrote: On Mon, Feb 09, 2015 at 05:36:07AM +, Jiang Liu wrote: Hi Rafael and Lorenzo, With more closer review, I suspect statement kfree(bus_range) in commit d2be00c0fb5a (of/pci: Free resources on failure in

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

On Mon, Feb 09, 2015 at 05:36:07AM +, Jiang Liu wrote: > Hi Rafael and Lorenzo, > With more closer review, I suspect statement "kfree(bus_range)" > in commit d2be00c0fb5a ("of/pci: Free resources on failure in > of_pci_get_host_bridge_resources()") may cause double free of bus_range >

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

Hi Rafael and Lorenzo, With more closer review, I suspect statement "kfree(bus_range)" in commit d2be00c0fb5a ("of/pci: Free resources on failure in of_pci_get_host_bridge_resources()") may cause double free of bus_range because bus_range will also be freed by kfree(window->res); Regards!

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

On Mon, Feb 09, 2015 at 03:19:33AM +, Rafael J. Wysocki wrote: > On Monday, February 09, 2015 01:26:42 PM Stephen Rothwell wrote: > > Hi Rafael, > > > > After merging the pm tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > In file included from

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

On Monday, February 09, 2015 10:53:05 AM Jiang Liu wrote: > > On 2015/2/9 10:26, Stephen Rothwell wrote: > > Hi Rafael, [cut] > >^ > > > > Caused by commit 14d76b68f281 ("PCI: Use common resource list > > management code instead of private implementation") interacting with > >

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

On Monday, February 09, 2015 01:26:42 PM Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from drivers/of/of_pci.c:1:0: > drivers/of/of_pci.c: In function

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

On 2015/2/9 10:26, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from drivers/of/of_pci.c:1:0: > drivers/of/of_pci.c: In function 'of_pci_get_host_bridge_resources': >

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

Hi Rafael, After merging the pm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from drivers/of/of_pci.c:1:0: drivers/of/of_pci.c: In function 'of_pci_get_host_bridge_resources': include/linux/list.h:447:43: error: dereferencing pointer to incomplete

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

On 2015/2/9 10:26, Stephen Rothwell wrote: Hi Rafael, After merging the pm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from drivers/of/of_pci.c:1:0: drivers/of/of_pci.c: In function 'of_pci_get_host_bridge_resources':

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

On Monday, February 09, 2015 01:26:42 PM Stephen Rothwell wrote: Hi Rafael, After merging the pm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from drivers/of/of_pci.c:1:0: drivers/of/of_pci.c: In function 'of_pci_get_host_bridge_resources':

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

Hi Rafael and Lorenzo, With more closer review, I suspect statement kfree(bus_range) in commit d2be00c0fb5a (of/pci: Free resources on failure in of_pci_get_host_bridge_resources()) may cause double free of bus_range because bus_range will also be freed by kfree(window-res); Regards! Gerry

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

On Mon, Feb 09, 2015 at 05:36:07AM +, Jiang Liu wrote: Hi Rafael and Lorenzo, With more closer review, I suspect statement kfree(bus_range) in commit d2be00c0fb5a (of/pci: Free resources on failure in of_pci_get_host_bridge_resources()) may cause double free of bus_range because

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

Hi Rafael, After merging the pm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from drivers/of/of_pci.c:1:0: drivers/of/of_pci.c: In function 'of_pci_get_host_bridge_resources': include/linux/list.h:447:43: error: dereferencing pointer to incomplete

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

On Monday, February 09, 2015 10:53:05 AM Jiang Liu wrote: On 2015/2/9 10:26, Stephen Rothwell wrote: Hi Rafael, [cut] ^ Caused by commit 14d76b68f281 (PCI: Use common resource list management code instead of private implementation) interacting with commit

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

On Mon, Feb 09, 2015 at 03:19:33AM +, Rafael J. Wysocki wrote: On Monday, February 09, 2015 01:26:42 PM Stephen Rothwell wrote: Hi Rafael, After merging the pm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from

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

On Monday, August 11, 2014 11:57:26 AM Stephen Rothwell wrote: > > --Sig_/+JDUwDarNoGtzkfUjWIyaKJ > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: quoted-printable > > Hi Rafael, > > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like

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

On Monday, August 11, 2014 11:57:26 AM Stephen Rothwell wrote: --Sig_/+JDUwDarNoGtzkfUjWIyaKJ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this:

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/mfd/sec-core.c: In function 'sec_pmic_suspend': drivers/mfd/sec-core.c:438:29: error: 'PM_SUSPEND_MEM' undeclared (first use in this function)

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/mfd/sec-core.c: In function 'sec_pmic_suspend': drivers/mfd/sec-core.c:438:29: error: 'PM_SUSPEND_MEM' undeclared (first use in this function)

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

On Wednesday, December 18, 2013 12:00:26 PM Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/acpi/nvs.c:15:27: fatal error: linux/acpi_io.h: No such file or > directory > #include >

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/acpi/nvs.c:15:27: fatal error: linux/acpi_io.h: No such file or directory #include ^ Caused by commit a99493647c1a ("Merge branch 'acpi-cleanup' into

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

Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/acpi/nvs.c:15:27: fatal error: linux/acpi_io.h: No such file or directory #include linux/acpi_io.h ^ Caused by commit a99493647c1a (Merge branch

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

On Wednesday, December 18, 2013 12:00:26 PM Stephen Rothwell wrote: Hi Rafael, After merging the pm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/acpi/nvs.c:15:27: fatal error: linux/acpi_io.h: No such file or directory #include linux/acpi_io.h

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

On Friday, July 05, 2013 11:24:58 AM Stephen Rothwell wrote: > Hi Rafael, Hi, > After merging the pm tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/gpu/drm/radeon/atombios_encoders.c: In function > 'radeon_atom_backlight_init': >

  1   2   >