linux-kernel - Re: HP accelerometer: split chip handling from HP ACPI interface

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:	Sat, 22 Nov 2008 01:25:56 +0100
From:	Éric Piel <eric.piel@...mplin-utc.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Pavel Machek <pavel@...e.cz>, linux-kernel@...r.kernel.org,
	trenn@...e.de, rpurdie@...ys.net, hmh@....eng.br
Subject: Re: HP accelerometer: split chip handling from HP ACPI interface

Andrew Morton schreef:
> On Fri, 21 Nov 2008 22:21:21 +0100
> Pavel Machek <pavel@...e.cz> wrote:
> 
>> This patch splits handling between chip-specific lis3lv02d and HP/ACPI
>> specific hp_accel.c.
> 
> umm, so?  What reason does anyone have for applying it?
Here is the log I have for the (old version) of pavel's patch:

The sensor can be accessed via various buses. In particular, SPI, I²C
and, on HP laptops, via a specific ACPI API (the only one currently
supported). Separate this latest platform from the core of the sensor
driver to allow support for the other bus type. The second, and more
direct goal is actually to be able to merge this part with the
hp-disk-leds driver, which has the same ACPI PNP number.

I'll try to follow with a patch doing the merge of the hp-disk-leds
driver, so that everything makes sense...

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