linux-kernel - Re: [PATCH v4] regulator: Add S5M8767A regulator driver

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]

Message-ID: <20120109213721.GD30766@opensource.wolfsonmicro.com>
Date:	Mon, 9 Jan 2012 21:37:21 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	Sangbeom Kim <sbkim73@...sung.com>, lrg@...com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] regulator: Add S5M8767A regulator driver

On Mon, Jan 09, 2012 at 10:08:21AM +0100, Samuel Ortiz wrote:
> On Sun, Jan 08, 2012 at 10:47:04PM -0800, Mark Brown wrote:

> > I've not reviwed it yet and there should be no dependency on the MFD
> > tree so no need to merge it via that - the fact that there's a Kconfig
> > dependency on the MFD means that the two can get merged in any order.

> Not only a Kconfig dependency, but also the regulator driver including some of
> the headers defined in the mfd patch:

> +#include <linux/mfd/s5m87xx/s5m-core.h>
> +#include <linux/mfd/s5m87xx/s5m-pmic.h>

> So, both need to get merged at the same time.

No, the point is that the Kconfig dependency means that the code
dependency isn't an issue - the code won't actually get built until the
MFD driver is merged.  But anyway it looks like the regulator will have
slipped to 3.4 so the MFD will already be in.
--
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/