public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	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>,
	Sangbeom Kim <sbkim73@samsung.com>
Subject: Re: [PATCH v2 0/3] regulator: s2mps11: Add support for S2MPS14 regulators
Date: Tue, 18 Mar 2014 18:34:53 +0000	[thread overview]
Message-ID: <20140318183453.GL11706@sirena.org.uk> (raw)
In-Reply-To: <1395164052.24909.11.camel@AMDC1943>

[-- Attachment #1: Type: text/plain, Size: 400 bytes --]

On Tue, Mar 18, 2014 at 06:34:12PM +0100, Krzysztof Kozlowski wrote:

> Lee Jones in his pull request [1] put also my changes for S2MPS14
> support in MFD sec-core driver. They are needed by this patchset for adding
> suppt for regulators on S2MPS14.

> Do you have time to look at these patches and apply them if they're OK
> (or ACK them)?

Possibly, though we are *very* near to the merge window.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-03-18 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 10:10 [PATCH v2 0/3] regulator: s2mps11: Add support for S2MPS14 regulators Krzysztof Kozlowski
2014-03-07 10:10 ` [PATCH v2 1/3] " Krzysztof Kozlowski
2014-03-07 10:10 ` [PATCH v2 2/3] regulator: s2mps11: Add set_suspend_disable for S2MPS14 Krzysztof Kozlowski
2014-03-07 10:10 ` [PATCH v2 3/3] Documentation: mfd: s2mps11: Document support " Krzysztof Kozlowski
2014-03-10  9:51   ` Lee Jones
2014-03-18 17:34 ` [PATCH v2 0/3] regulator: s2mps11: Add support for S2MPS14 regulators Krzysztof Kozlowski
2014-03-18 18:34   ` Mark Brown [this message]
2014-03-19 13:03 ` Mark Brown

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=20140318183453.GL11706@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.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