From: Mark Brown <broonie@kernel.org>
To: John Crispin <blogic@openwrt.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
chen.zhong@mediatek.com, HenryC.Chen@mediatek.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH V5 2/2] regulator: mt6323: Add support for MT6323 regulator
Date: Tue, 9 Feb 2016 12:36:49 +0000 [thread overview]
Message-ID: <20160209123649.GD13270@sirena.org.uk> (raw)
In-Reply-To: <1454874037-38905-2-git-send-email-blogic@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 229 bytes --]
On Sun, Feb 07, 2016 at 08:40:37PM +0100, John Crispin wrote:
> * remove the code allows mode changes
That was excessive, there's no problem having set_mode() operations and
we can currently use them for static configurations.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 2/2] regulator: mt6323: Add support for MT6323 regulator
Date: Tue, 9 Feb 2016 12:36:49 +0000 [thread overview]
Message-ID: <20160209123649.GD13270@sirena.org.uk> (raw)
In-Reply-To: <1454874037-38905-2-git-send-email-blogic@openwrt.org>
On Sun, Feb 07, 2016 at 08:40:37PM +0100, John Crispin wrote:
> * remove the code allows mode changes
That was excessive, there's no problem having set_mode() operations and
we can currently use them for static configurations.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160209/952d1a9e/attachment.sig>
next prev parent reply other threads:[~2016-02-09 12:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 19:40 [PATCH V5 1/2] regulator: Add document for MT6323 regulator John Crispin
2016-02-07 19:40 ` John Crispin
2016-02-07 19:40 ` John Crispin
2016-02-07 19:40 ` [PATCH V5 2/2] regulator: mt6323: Add support " John Crispin
2016-02-07 19:40 ` John Crispin
2016-02-09 12:36 ` Mark Brown [this message]
2016-02-09 12:36 ` Mark Brown
2016-02-08 21:24 ` [PATCH V5 1/2] regulator: Add document " Rob Herring
2016-02-08 21:24 ` Rob Herring
2016-02-08 21:24 ` Rob Herring
2016-02-09 12:41 ` Mark Brown
2016-02-09 12:41 ` Mark Brown
2016-02-09 12:45 ` John Crispin
2016-02-09 12:45 ` John Crispin
2016-02-09 15:17 ` Mark Brown
2016-02-09 15:17 ` 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=20160209123649.GD13270@sirena.org.uk \
--to=broonie@kernel.org \
--cc=HenryC.Chen@mediatek.com \
--cc=blogic@openwrt.org \
--cc=chen.zhong@mediatek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.