| 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: <20120521090844.GA12015@sortiz-mobl> Date: Mon, 21 May 2012 11:08:44 +0200 From: Samuel Ortiz <sameo@...ux.intel.com> To: Johan Hovold <jhovold@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/2] mfd: Add r_select to lm3533 platform data Hi Johan, On Mon, May 21, 2012 at 10:45:39AM +0200, Johan Hovold wrote: > On Sun, May 20, 2012 at 03:13:37PM +0200, Samuel Ortiz wrote: > > Hi Johan, > > > > On Fri, May 18, 2012 at 08:22:45PM +0200, Johan Hovold wrote: > > > Add resistor-select parameter to the platform data. > > > > > > Signed-off-by: Johan Hovold <jhovold@...il.com> > > > --- > > > > > > Hi Samuel, > > > > > > I believe this one needs to go in through mfd as the iio driver > > > destined for staging-next depends on it. > > It should go along with the iio driver if there is a build dependency. > > No doing so will prevent the tree from being bisectable. > > The sub-drivers already depend on mfd to build as this is where the > header file resides. I haven't looked at it, but if the iio driver Kconfig entry depends on MFD_LM3533, then I can take this change in as no one will be able to build your iio driver until the MFD driver is merged. Is that the case ? Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ -- 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