From: Mark Brown <broonie@kernel.org>
To: James Ban <james.ban.opensource@diasemi.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Support Opensource <support.opensource@diasemi.com>,
LKML <linux-kernel@vger.kernel.org>,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH V4] regulator: da9211: Add gpio control for enable/disable of buck
Date: Wed, 28 Jan 2015 17:38:31 +0000 [thread overview]
Message-ID: <20150128173831.GB21293@sirena.org.uk> (raw)
In-Reply-To: <201501280038.t0S0cOqr040885@krsrvapps-01.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 149 bytes --]
On Wed, Jan 28, 2015 at 09:28:08AM +0900, James Ban wrote:
> This is a patch for adding gpio control about enable/disable of buck.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-01-29 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 0:28 [PATCH V4] regulator: da9211: Add gpio control for enable/disable of buck James Ban
2015-01-28 17:38 ` Mark Brown [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=20150128173831.GB21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=david.chen@diasemi.com \
--cc=james.ban.opensource@diasemi.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=support.opensource@diasemi.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;
as well as URLs for NNTP newsgroup(s).