public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: John Crispin <blogic@openwrt.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Chen Zhong <chen.zhong@mediatek.com>,
	lee.jones@linaro.org
Subject: Re: [PATCH V7 2/2] regulator: mt6323: Add support for MT6323 regulator
Date: Fri, 26 Feb 2016 11:10:19 +0900	[thread overview]
Message-ID: <20160226021019.GD18327@sirena.org.uk> (raw)
In-Reply-To: <1456396631-12788-2-git-send-email-blogic@openwrt.org>

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

On Thu, Feb 25, 2016 at 11:37:11AM +0100, John Crispin wrote:

> This patch needs to be merged post-rc1 as it depends on the MFD series of
> the PMIC which is already inside Lee's tree pending the PR.

Please resubmit when that has happened or arrange with Lee (who I've
added to the CC) for a tag I can pull with the required dependencies.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-02-26  2:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 10:37 [PATCH V7 1/2] regulator: Add document for MT6323 regulator John Crispin
2016-02-25 10:37 ` [PATCH V7 2/2] regulator: mt6323: Add support " John Crispin
2016-02-26  2:10   ` Mark Brown [this message]
2016-03-02 18:07 ` [PATCH V7 1/2] regulator: Add document " Rob Herring
2016-03-02 18:13   ` John Crispin
  -- strict thread matches above, loose matches on Subject: below --
2016-02-22 12:56 John Crispin
2016-02-22 12:56 ` [PATCH V7 2/2] regulator: mt6323: Add support " John Crispin

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=20160226021019.GD18327@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=blogic@openwrt.org \
    --cc=chen.zhong@mediatek.com \
    --cc=lee.jones@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox