From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
lrg@ti.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] regulator: Add S5M8767A regulator driver
Date: Mon, 9 Jan 2012 21:37:21 +0000 [thread overview]
Message-ID: <20120109213721.GD30766@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120109090821.GK13679@sortiz-mobl>
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.
next prev parent reply other threads:[~2012-01-09 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 6:05 [PATCH v4] regulator: Add S5M8767A regulator driver Sangbeom Kim
2012-01-08 23:16 ` Samuel Ortiz
2012-01-09 6:47 ` Mark Brown
2012-01-09 9:08 ` Samuel Ortiz
2012-01-09 21:37 ` Mark Brown [this message]
2012-01-09 23:43 ` Samuel Ortiz
2012-01-09 7:25 ` Mark Brown
2012-01-09 8:35 ` Sangbeom Kim
2012-01-09 8:41 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120109213721.GD30766@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.com \
--cc=sbkim73@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).