From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Tomasz Figa <t.figa@samsung.com>,
Yadwinder Singh Brar <yadi.brar@samsung.com>,
Sachin Kamat <sachin.kamat@linaro.org>
Subject: Re: [PATCH 2/3] regulator: s2mps11: Add set_suspend_disable for S2MPS14
Date: Fri, 7 Mar 2014 09:51:39 +0800 [thread overview]
Message-ID: <20140307015139.GS13126@sirena.org.uk> (raw)
In-Reply-To: <1394099334.25853.1.camel@AMDC1943>
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
On Thu, Mar 06, 2014 at 10:48:54AM +0100, Krzysztof Kozlowski wrote:
> Anyway can you look at other two patches and apply them if they are OK?
> They don't depend on this.
There appears to be some external dependency for the definition of
macros like S2MPS14X?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-07 1:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 9:22 [PATCH 0/3] regulator: s2mps11: Add support for S2MPS14 regulators Krzysztof Kozlowski
2014-03-05 9:22 ` [PATCH 1/3] " Krzysztof Kozlowski
2014-03-05 9:22 ` [PATCH 2/3] regulator: s2mps11: Add set_suspend_disable for S2MPS14 Krzysztof Kozlowski
2014-03-05 9:55 ` Lee Jones
2014-03-06 9:38 ` Mark Brown
2014-03-06 9:48 ` Krzysztof Kozlowski
2014-03-07 1:51 ` Mark Brown [this message]
2014-03-07 7:28 ` Krzysztof Kozlowski
2014-03-10 9:47 ` Lee Jones
2014-03-06 14:42 ` Krzysztof Kozlowski
2014-03-07 2:37 ` Mark Brown
2014-03-07 10:15 ` Krzysztof Kozlowski
2014-03-05 9:22 ` [PATCH 3/3] Documentation: mfd: s2mps11: Document support " Krzysztof Kozlowski
2014-03-05 10:04 ` Sachin Kamat
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=20140307015139.GS13126@sirena.org.uk \
--to=broonie@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sachin.kamat@linaro.org \
--cc=sameo@linux.intel.com \
--cc=sbkim73@samsung.com \
--cc=t.figa@samsung.com \
--cc=yadi.brar@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