From: John Crispin <john@phrozen.org>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V8 1/2] regulator: Add document for MT6323 regulator
Date: Mon, 11 Jul 2016 20:55:24 +0200 [thread overview]
Message-ID: <cef78bd8-9a4a-e848-d7cb-13a27127f11e@phrozen.org> (raw)
In-Reply-To: <20160711180805.GG3701@sirena.org.uk>
On 11/07/2016 20:08, Mark Brown wrote:
> On Mon, Jul 11, 2016 at 02:29:38PM +0200, John Crispin wrote:
>
>> This is a resend as V7 was dropped due to a merge order conflict.
>
> What were the dependencies and why will simply resending this resolve
> them?
>
Hi Mark,
the dependency was the mt6323 support inside the mt6397 MFD device [1]
and the headers that it included. this has been merged so the regulator
driver is good to go for 4.8
John
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/mfd/mt6397-core.c?id=refs/tags/v4.7-rc7
>
>
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
>
next prev parent reply other threads:[~2016-07-11 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 12:29 [PATCH V8 1/2] regulator: Add document for MT6323 regulator John Crispin
[not found] ` <1468240179-7558-1-git-send-email-john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org>
2016-07-11 18:08 ` Mark Brown
2016-07-11 18:55 ` John Crispin [this message]
[not found] ` <cef78bd8-9a4a-e848-d7cb-13a27127f11e-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org>
2016-07-11 19:22 ` Mark Brown
2016-07-11 20:31 ` John Crispin
2016-07-11 21:07 ` 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=cef78bd8-9a4a-e848-d7cb-13a27127f11e@phrozen.org \
--to=john@phrozen.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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).