linux-kernel - Re: [PATCH v2] drm/nouveau: always select ACPI

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]

Message-ID: <20130205162206.GJ4827@pd.tnic>
Date:	Tue, 5 Feb 2013 17:22:06 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Maarten Lankhorst <maarten.lankhorst@...onical.com>
Cc:	dri-devel@...ts.freedesktop.org,
	lkml <linux-kernel@...r.kernel.org>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: [PATCH v2] drm/nouveau: always select ACPI_VIDEO if ACPI is
 enabled.

On Tue, Feb 05, 2013 at 04:38:35PM +0100, Maarten Lankhorst wrote:
> Argh, next attempt, based on i915's Kconfig.
> 
> It seems that not only I have to select ACPI_VIDEO, I also have to select all the dependencies.
> Is this a Kconfig bug or working as intended? i915 seems to have a workaround, so I copied it from
> there. Except it's currently missing select THERMAL, so I guess it didn't get updated when that got
> added.
> 
> ---->8
> Having nouveau builtin would still allow ACPI_VIDEO to be used as external module
> if some of the deps for acpi_video have not been met, which would result in a linking
> failure. Solve this by selecting all dependencies as well.
> 
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@...onical.com>

Yep, this takes care of all deps,

Tested-by: Borislav Petkov <bp@...e.de>

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/