From: Mark Brown <broonie@kernel.org>
To: Tomasz Figa <t.figa@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kukjin Kim <kgene.kim@samsung.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Grant Likely <grant.likely@linaro.org>,
Jiri Kosina <jkosina@suse.cz>,
Liam Girdwood <lgirdwood@gmail.com>,
Masanari Iida <standby24x7@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
rtc-linux@googlegroups.com, Russell King <linux@arm.linux.org.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH v3 2/3] regulator: max8998: Use arrays for specifying voltages in platform data
Date: Mon, 24 Jun 2013 15:54:29 +0100 [thread overview]
Message-ID: <20130624145429.GP27646@sirena.org.uk> (raw)
In-Reply-To: <1372077594-17052-3-git-send-email-t.figa@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
On Mon, Jun 24, 2013 at 02:39:53PM +0200, Tomasz Figa wrote:
> This patch modifies the platform data of max8998 to use arrays for
> specifying predefined voltages of buck1 and buck2 instead of separate
> field for each voltage.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-24 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 12:39 [PATCH v3 0/3] regulator: max8998: Add support for Device Tree Tomasz Figa
2013-06-24 12:39 ` [PATCH v3 1/3] mfd: Add irq domain support for max8998 interrupts Tomasz Figa
2013-06-24 12:39 ` [PATCH v3 2/3] regulator: max8998: Use arrays for specifying voltages in platform data Tomasz Figa
2013-06-24 14:54 ` Mark Brown [this message]
2013-06-24 12:39 ` [PATCH v3 3/3] mfd: max8998: Add support for Device Tree Tomasz Figa
2013-06-24 14:54 ` Sachin Kamat
2013-06-25 13:46 ` [PATCH v4 " Tomasz Figa
2013-06-25 14:07 ` Tomasz Figa
2013-06-25 14:08 ` [PATCH RESEND " Tomasz Figa
2013-06-24 15:04 ` [PATCH v3 " Mark Brown
2013-06-27 8:01 ` [PATCH v3 0/3] regulator: " 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=20130624145429.GP27646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a.zummo@towertech.it \
--cc=grant.likely@linaro.org \
--cc=jkosina@suse.cz \
--cc=kgene.kim@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=standby24x7@gmail.com \
--cc=t.figa@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
Powered by JetHome