| 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
| ||
|
Message-ID: <20110203093154.GC21591@opensource.wolfsonmicro.com> Date: Thu, 3 Feb 2011 09:31:54 +0000 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Andres Salomon <dilinger@...ued.net> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, Samuel Ortiz <sameo@...ux.intel.com>, linux-kernel@...r.kernel.org, Peter Ujfalusi <peter.ujfalusi@...ia.com>, Liam Girdwood <lrg@...mlogic.co.uk>, Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>, Timur Tabi <timur@...escale.com>, linux-input@...r.kernel.org, alsa-devel@...a-project.org Subject: Re: [PATCH 12/19] twl4030: mfd_cell is now implicitly available to drivers On Wed, Feb 02, 2011 at 11:03:26PM -0800, Andres Salomon wrote: > Dmitry Torokhov <dmitry.torokhov@...il.com> wrote: > > Then they are doing it incorrectly. One possible way is to have parent > > device carry relevant data in its drvdata and have children get it > > from there. > I believe some drivers are even using the parent device already. See > drivers/leds/leds-mc13783.c, for example, whose parent device drvdata > is used to pass around a struct mc13783 to its children. Sounds > like a possibility, will need to look into it further. That's the current best practice approach. -- 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/
Powered by blists - more mailing lists