linux-kernel - Re: [PATCH] x86: unification of cfufreq/Kconfig

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:	Wed, 7 Nov 2007 08:18:01 +0100
From:	Adrian Bunk <bunk@...nel.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: unification of cfufreq/Kconfig

On Wed, Nov 07, 2007 at 08:06:44AM +0100, Sam Ravnborg wrote:
> On Wed, Nov 07, 2007 at 07:02:20AM +0100, Adrian Bunk wrote:
> > On Wed, Nov 07, 2007 at 12:01:12AM +0100, Sam Ravnborg wrote:
> > >...
> > >  config X86_SPEEDSTEP_CENTRINO
> > > -	tristate "Intel Enhanced SpeedStep"
> > > +	tristate "Intel Enhanced SpeedStep (deprecated)"
> > >  	select CPU_FREQ_TABLE
> > > -	select X86_SPEEDSTEP_CENTRINO_TABLE
> > > +	select X86_SPEEDSTEP_CENTRINO_TABLE if X86_32
> > > +	depends on X86_64 && ACPI_PROCESSOR
> > >...
> > 
> > No.
> > 
> > 	depends on ACPI_PROCESSOR if X86_64
> 
> Gives syntax error.

That happens when you review something without trying it...

	depends on (ACPI_PROCESSOR || !X86_64)

> 	Sam

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/