linux-kernel - Re: [PATCH V8 1/2] regulator: Add document for MT6323 regulator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Jul 2016 22:07:54 +0100
From:	Mark Brown <broonie@...nel.org>
To:	John Crispin <john@...ozen.org>
Cc:	devicetree@...r.kernel.org, linux-mediatek@...ts.infradead.org,
	Liam Girdwood <lgirdwood@...il.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V8 1/2] regulator: Add document for MT6323 regulator

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.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)