linux-kernel - Re: ACPI video.c brightness handler conflicts with toshiba

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

Date:	Fri, 07 Nov 2008 22:29:53 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Thomas Renninger <trenn@...e.de>, toshiba_acpi@...ebeam.org,
	linux-acpi@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: ACPI video.c brightness handler conflicts with toshiba_acpi



> > Do you have a pointer to those patches?
> > 
> 
> So far I am running with these commits from git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-acpi-2.6:
> 
> commit f43d728731c691772ddc29e50d25c68a859935b5
> Author: Thomas Renninger <trenn@...e.de>
> Date:   Fri Aug 1 17:37:55 2008 +0200
> 
>     Check for ACPI backlight support otherwise use vendor ACPI drivers
> 
> 
> commit ad9ed8385ed6ec5be8da7094db911c824258ceec
> Author: Thomas Renninger <trenn@...e.de>
> Date:   Fri Aug 1 17:37:54 2008 +0200
> 
>     ACPI: video: Ignore devices that aren't present in hardware
> 
> I have been waiting for in-tree inclusion to submit patches for
> toshiba_acpi against stable base.

Ah, the commit id's above solved the mystery.
It looks like andi checked these patches directly into his
"test" branch rather than a topic branch.  eg. they were
sitting on top of the old pcc_acpi driver etc.

So I lost them when I deleted the old test branch
in order to merge the updated topic branches
into a new test branch.

-Len

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