From: Mark Brown <broonie@kernel.org>
To: Chen Zhong <chen.zhong@mediatek.com>, John Crispin <blogic@openwrt.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Applied "regulator: mt6323: Add support for MT6323 regulator" to the regulator tree
Date: Tue, 15 Mar 2016 09:32:00 +0000 [thread overview]
Message-ID: <20160315093200.GK2566@sirena.org.uk> (raw)
In-Reply-To: <E1aflHq-0005Ze-Hg@debutante>
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
On Tue, Mar 15, 2016 at 09:29:10AM +0000, Mark Brown wrote:
> The patch
>
> regulator: mt6323: Add support for MT6323 regulator
>
> has been applied to the regulator tree at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
Sorry, this is my scripts not coping with dropped branches - the issue
with the MFD changes not being there is still a thing. Please resend
when that is resolved.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-15 9:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 11:37 [PATCH V6 1/2] regulator: Add document for MT6323 regulator John Crispin
2016-02-17 11:37 ` [PATCH V6 2/2] regulator: mt6323: Add support " John Crispin
2016-02-17 19:13 ` Applied "regulator: mt6323: Add support for MT6323 regulator" to the regulator tree Mark Brown
2016-03-15 9:29 ` Mark Brown
2016-03-15 9:32 ` Mark Brown [this message]
2016-03-15 9:52 ` John Crispin
2016-02-17 19:13 ` Applied "regulator: Add document " Mark Brown
2016-02-18 14:36 ` [PATCH V6 1/2] regulator: Add document for MT6323 regulator Rob Herring
2016-02-18 14:50 ` John Crispin
2016-02-21 0:38 ` Mark Brown
2016-03-15 9:29 ` Applied "regulator: Add document for MT6323 regulator" to the regulator tree Mark Brown
2016-07-18 12:40 [PATCH V10 2/2] regulator: mt6323: Add support for MT6323 regulator John Crispin
2016-07-18 12:46 ` Applied "regulator: mt6323: Add support for MT6323 regulator" to the regulator tree 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=20160315093200.GK2566@sirena.org.uk \
--to=broonie@kernel.org \
--cc=blogic@openwrt.org \
--cc=chen.zhong@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
/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).