From: Lee Jones <lee.jones@linaro.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Mark Brown <broonie@kernel.org>, Milo Kim <milo.kim@ti.com>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v4 0/4] LP3943 MFD driver for a GPIO expander and a PWM generator
Date: Fri, 6 Dec 2013 16:24:32 +0000 [thread overview]
Message-ID: <20131206162432.GA11060@lee--X1> (raw)
In-Reply-To: <20131206132405.GC30960@ulmo.nvidia.com>
On Fri, 06 Dec 2013, Thierry Reding wrote:
> On Thu, Dec 05, 2013 at 09:43:41PM +0000, Mark Brown wrote:
> > On Wed, Dec 04, 2013 at 11:34:32AM +0100, Thierry Reding wrote:
> > > On Wed, Sep 25, 2013 at 01:22:55PM +0900, Milo Kim wrote:
> >
> > > > mfd: add LP3943 MFD driver
> > > > gpio: add LP3943 I2C GPIO expander driver
> > > > pwm: add LP3943 PWM driver
> > > > Documentation: add LP3943 DT bindings and document
> >
> > > I suspect that given the build-time dependencies Lee may want to take
> > > all four patches through the MFD tree, so I've acked the PWM parts.
> >
> > FWIW this isn't an issue with new MFDs - since the function drivers will
> > depend on the core driver it's not possible to enable them in Kconfig
> > until the core driver is also merged and you don't get bisect issues.
>
> Right. I hadn't thought about that. Thanks for mentioning it.
I have applied them all with the relevant Acks in any case.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2013-12-06 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 4:22 [PATCH v4 0/4] LP3943 MFD driver for a GPIO expander and a PWM generator Milo Kim
2013-09-25 4:22 ` Milo Kim
2013-09-25 4:22 ` Milo Kim
2013-12-03 23:27 ` Milo Kim
2013-12-03 23:27 ` Milo Kim
2013-12-04 8:05 ` Lee Jones
2013-12-04 10:34 ` Thierry Reding
2013-12-04 10:50 ` Lee Jones
2013-12-05 21:43 ` Mark Brown
2013-12-06 13:24 ` Thierry Reding
2013-12-06 16:24 ` Lee Jones [this message]
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=20131206162432.GA11060@lee--X1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=sameo@linux.intel.com \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.