linux-kernel - lis3's ACPI dependency

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

Message-ID: <20090301132953.GF20813@buzzloop.caiaq.de>
Date:	Sun, 1 Mar 2009 14:29:53 +0100
From:	Daniel Mack <daniel@...aq.de>
To:	Pavel Machek <pavel@...e.cz>,
	Éric Piel <eric.piel@...mplin-utc.net>
Cc:	linux-kernel@...r.kernel.org
Subject: lis3's ACPI dependency

Hi Pavel, Eric,

are there any plans to free the lis3 driver from its ACPI dependency?
In fact, this device is I2C/SPI connected which the ACPI layer seems to
hide from the driver, but to use it on embedded devices, the bus drivers
must be used directly and the dependeny seems entirely unnecessary
anyway.

Also I got the feeling that using a globally exported 'adev' symbol all
over the different layers is not the best practice - I suspect all the
occasions could be solved with private pointers and/or container_of().
Isn't there any cleanup pending?

Thanks and best regards,
Daniel

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