linux-kernel - Re: Fwd: Re: Linux 2.6.22-rc1

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20070516024101.GC3971@inferi.kami.home>
Date:	Wed, 16 May 2007 11:41:01 +0900
From:	Mattia Dongili <malattia@...ux.it>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	linux-acpi@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	sam@...nborg.org
Subject: Re: Fwd: Re: Linux 2.6.22-rc1

On Tue, May 15, 2007 at 10:46:21AM -0700, Randy Dunlap wrote:
> On Wed, 16 May 2007 00:42:08 +0900 Mattia Dongili wrote:
...
> > Given the drivers/acpi/Kconfig portion
> > 
> >   if ACPI
> >   ...
> >   config ACPI_EC
> >           bool
> >           default y
> >           help
> >             ...
> >   
> >   config ACPI_POWER
> >           bool
> >           default y
> >   
> >   config ACPI_SYSTEM
> >           bool
> >           default y
> >           help
> > 	  ...
> >   ...
> >   endif
> > 
> > I'd expect the 3 symbols to be all set when CONFIG_ACPI=y.
> > What am I overseeing?
> 
> I think that this is just 'make randconfig' throwing a curve ball.
> ACPI depends on PM, but PM=n.  In my experience, randconfig is a
> good tool for testing oddball configs, but the results are not
> always something that is fixable or needs to be fixed.

It looks like Kconfig does the right thing on i386 though. Not the same
on x84_64.

-- 
mattia
:wq!
-
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/