From: Mark Brown <broonie@kernel.org>
To: John Crispin <john@phrozen.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:22:11 +0100 [thread overview]
Message-ID: <20160711192211.GI3701@sirena.org.uk> (raw)
In-Reply-To: <cef78bd8-9a4a-e848-d7cb-13a27127f11e@phrozen.org>
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
On Mon, Jul 11, 2016 at 08:55:24PM +0200, John Crispin wrote:
> 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?
> 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
No, that's not resolving the dependencies - if I apply these patches
without the dependencies in the regulator tree that will still break the
build for my tree until after the merge window. It'll also break Linus'
tree if (as is normal) I send my pull requests early on. I'd need to
merge the MFD commits into my tree which would need coordination with
Lee, he'd need to make a tag for me to pull in.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-11 19:22 UTC|newest]
Thread overview: 8+ 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
2016-07-11 12:29 ` [PATCH V8 2/2] regulator: mt6323: Add support " John Crispin
2016-07-11 21:12 ` Mark Brown
2016-07-11 18:08 ` [PATCH V8 1/2] regulator: Add document " Mark Brown
2016-07-11 18:55 ` John Crispin
2016-07-11 19:22 ` Mark Brown [this message]
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=20160711192211.GI3701@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.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).