linux-kernel - Re: [-mm patch] cpu

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 2 Mar 2007 16:24:59 +0000
From:	Frederik Deweerdt <deweerdt@...e.fr>
To:	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, abelay@...ell.com,
	shaohua.li@...el.com, len.brown@...el.com
Subject: Re: [-mm patch] cpu_idle: fix build break

On Fri, Mar 02, 2007 at 07:24:28AM -0800, Venkatesh Pallipadi wrote:
> On Fri, Mar 02, 2007 at 02:40:07PM +0000, Frederik Deweerdt wrote:
> > On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote:
> > > +git-acpi-fix-cpuidle-borkage.patch
> > This attached patch might be needed too, the build breaks if
> > !CONFIG_HOTPLUG_CPU and CONFIG_CPU_IDLE
> >  
> >   CC      drivers/cpuidle/cpuidle.o
> > drivers/cpuidle/cpuidle.c: In function 'cpuidle_init':
> > drivers/cpuidle/cpuidle.c:272: erreur: 'cpuidle_cpu_notifier' undeclared (first use in this function)
> > drivers/cpuidle/cpuidle.c:272: erreur: (Each undeclared identifier is reported only once
> > drivers/cpuidle/cpuidle.c:272: erreur: for each function it appears in.)
> > make[2]: *** [drivers/cpuidle/cpuidle.o] Erreur 1
> > make[1]: *** [drivers/cpuidle] Erreur 2
> > make: *** [drivers] Erreur 2
> >
> 
> Thanks for catching this breakage. Patch below should be the proper fix.
Yep, works for me.

Regards,
Frederik
-
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/