linux-kernel - Re: Updating Raspberry Pi trees pulled for -next

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]

Message-ID: <8737oo64ud.fsf@eliezer.anholt.net>
Date:	Tue, 07 Jun 2016 14:56:10 -0700
From:	Eric Anholt <eric@...olt.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-rpi-kernel@...ts.infradead.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Florian Fainelli <f.fainelli@...il.com>,
	Stephen Warren <swarren@...dotorg.org>
Subject: Re: Updating Raspberry Pi trees pulled for -next

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> Hi Eric,
>
> On Mon, 06 Jun 2016 15:08:26 -0700 Eric Anholt <eric@...olt.net> wrote:
>>
>> I was going to bother you to add a bunch more trees to pull into -next
>> now that I'll be merging arm64 changes for the Raspberry Pi 3, but
>> instead I've decided to start using the maint-scripts to make generating
>> a single for-next branch trivial.
>
> Thanks for that.
>
>> So, could you replace all of my -next branches you're pulling with:
>> 
>> git://github.com/anholt/linux.git#for-next
>
> Done.

In next-20160607 I see drm-vc4-next merged separately, which I also
included in for-next.  I think it would be best to drop that one, too.

Thanks!

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