From: Samuel Ortiz <sameo@linux.intel.com>
To: Johan Hovold <jhovold@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: Add r_select to lm3533 platform data
Date: Mon, 21 May 2012 11:08:44 +0200 [thread overview]
Message-ID: <20120521090844.GA12015@sortiz-mobl> (raw)
In-Reply-To: <20120521084539.GB21033@localhost>
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@gmail.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/
next prev parent reply other threads:[~2012-05-21 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 18:22 [PATCH 1/2] mfd: Add r_select to lm3533 platform data Johan Hovold
2012-05-18 18:22 ` [PATCH 2/2] mfd: Mark two lm3533 zone registers as volatile Johan Hovold
2012-05-20 13:20 ` Samuel Ortiz
2012-05-20 13:13 ` [PATCH 1/2] mfd: Add r_select to lm3533 platform data Samuel Ortiz
2012-05-21 8:45 ` Johan Hovold
2012-05-21 9:08 ` Samuel Ortiz [this message]
2012-05-21 9:41 ` Johan Hovold
2012-05-22 21:52 ` Samuel Ortiz
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=20120521090844.GA12015@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=jhovold@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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