Updating Raspberry Pi trees pulled for -next

Updating Raspberry Pi trees pulled for -next

[Eric Anholt]

[-- Attachment #1: Type: text/plain, Size: 367 bytes --]

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.

So, could you replace all of my -next branches you're pulling with:

git://github.com/anholt/linux.git#for-next

Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

Updating Raspberry Pi trees pulled for -next

[Eric Anholt]

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.

So, could you replace all of my -next branches you're pulling with:

git://github.com/anholt/linux.git#for-next

Thanks!
-------------- 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-arm-kernel/attachments/20160606/663c155a/attachment-0001.sig>

Re: Updating Raspberry Pi trees pulled for -next

[Stephen Rothwell]

Hi Eric,

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

-- 
Cheers,
Stephen Rothwell

Updating Raspberry Pi trees pulled for -next

[Stephen Rothwell]

Hi Eric,

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

-- 
Cheers,
Stephen Rothwell

Re: Updating Raspberry Pi trees pulled for -next

[Eric Anholt]

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

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

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

Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

Updating Raspberry Pi trees pulled for -next

[Eric Anholt]

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

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

Thanks!
-------------- 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-arm-kernel/attachments/20160607/3182dede/attachment.sig>

Re: Updating Raspberry Pi trees pulled for -next

[Stephen Rothwell]

Hi Eric,

On Tue, 07 Jun 2016 14:56:10 -0700 Eric Anholt <eric@anholt.net> wrote:
>
> 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.

OK, I was assuming that it was being merged via the drm tree.  I will
drop it today.

-- 
Cheers,
Stephen Rothwell

Updating Raspberry Pi trees pulled for -next

[Stephen Rothwell]

Hi Eric,

On Tue, 07 Jun 2016 14:56:10 -0700 Eric Anholt <eric@anholt.net> wrote:
>
> 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.

OK, I was assuming that it was being merged via the drm tree.  I will
drop it today.

-- 
Cheers,
Stephen Rothwell