Updating Raspberry Pi trees pulled for -next

Eric Anholt eric at anholt.net
Tue Jun 7 14:56:10 PDT 2016

Stephen Rothwell <sfr at canb.auug.org.au> writes:

> Hi Eric,
> On Mon, 06 Jun 2016 15:08:26 -0700 Eric Anholt <eric at anholt.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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-rpi-kernel/attachments/20160607/3182dede/attachment.sig>

More information about the linux-rpi-kernel mailing list