linux-kernel - Re: RFC: Working around dynamic device allocation in i2c. Interaction with other subystems.

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:	Mon, 19 Jan 2009 19:37:05 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	linux-i2c@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	eric miao <eric.y.miao@...il.com>,
	Jean Delvare <khali@...ux-fr.org>
Subject: Re: RFC: Working around dynamic device allocation in i2c.  Interaction with other subystems.

On Mon, Jan 19, 2009 at 07:18:39PM +0000, Jonathan Cameron wrote:

> 1) Relax the constraints that the token used for device identification
>    in subsystems using the regulators approach to a void * and use
>    the platform data pointer of an i2c device.  Note this requires
>    every device which may need a regulator to have platform data.
>    Whilst this would work, it is far from ideal.

This would also remove the ability of the APIs using this to use the
struct device for other things like showing what they're doing in sysfs
or use dev_printk.
--
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/