From: Samuel Ortiz <sameo@linux.intel.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Krystian Garbaciak <krystian.garbaciak@diasemi.com>
Subject: Re: [PATCH v3 0/6] Add Dialog DA9063 core and regulator drivers
Date: Tue, 20 Aug 2013 03:18:49 +0200 [thread overview]
Message-ID: <20130820011849.GC13324@zurbaran> (raw)
In-Reply-To: <1375117247-6376-1-git-send-email-p.zabel@pengutronix.de>
Hi Philipp,
On Mon, Jul 29, 2013 at 07:00:41PM +0200, Philipp Zabel wrote:
> Hi,
>
> here is the third round of the DA9063 mfd core and regulator patches, with the
> following changes since v2:
> - Split DA9063 core driver patch into three more digestible parts
> (register definitions, core mfd/i2c driver, regmap irqchip support)
I applied those 3 patches to mfd-next, and dropped patch #6.
> - Removed 32k clock output from the regulator driver
> - Added device tree binding documentation
I suppose I should carry this one as well. I'll wait a bit more to see
if we get some more feedback about it.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2013-08-20 1:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 17:00 Philipp Zabel
2013-07-29 17:00 ` [PATCH v3 1/6] mfd: da9063: Add register definitions for DA9063 driver Philipp Zabel
2013-07-29 17:00 ` [PATCH v3 2/6] mfd: da9063: Add Dialog DA9063 core driver Philipp Zabel
2013-07-29 17:00 ` [PATCH v3 3/6] mfd: da9063: Add IRQ support Philipp Zabel
2013-07-29 17:00 ` [PATCH v3 4/6] regulator: da9063: Add Dialog DA9063 voltage regulators support Philipp Zabel
2013-08-29 18:35 ` Mark Brown
2013-07-29 17:00 ` [PATCH v3 5/6] Documentation: Add device tree bindings for DA9063 PMIC Philipp Zabel
2013-07-29 17:00 ` [PATCH v3 6/6] mfd: da9063: add 32 kHz output clock to clock tree Philipp Zabel
2013-07-29 18:15 ` Mark Brown
2013-08-02 11:50 ` Philipp Zabel
2013-08-20 1:18 ` Samuel Ortiz [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=20130820011849.GC13324@zurbaran \
--to=sameo@linux.intel.com \
--cc=broonie@kernel.org \
--cc=krystian.garbaciak@diasemi.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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
all inboxes | Powered by JetHome®