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 22:07:54 +0100 [thread overview]
Message-ID: <20160711210754.GA9976@sirena.org.uk> (raw)
In-Reply-To: <c1acbf13-93a0-4257-ee48-4885a87fede5@phrozen.org>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On Mon, Jul 11, 2016 at 10:31:45PM +0200, John Crispin wrote:
> maybe i am missing something here, but i can see the dependencies inside
> the for-next branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git. is
> this not the tree i should base patches on for v4.8 ?
Oh, so these aren't things that Lee just applied but rather things that
have propagated through? You didn't say what commits you were talking
about, you linked to a long gitweb URL that would have been difficult to
paste due to wrapping. This sort of thing is why it's really helpful to
make your e-mails directly human readable, saying something like "these
depend on change X which is in Linus' tree now" would've made this
clear.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-07-11 21:07 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
[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 [this message]
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=20160711210754.GA9976@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).