Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1415511 > unrolled thread
| Started by | Eric Anholt <eric@anholt.net> |
|---|---|
| First post | 2016-06-07 00:10 +0200 |
| Last post | 2016-06-08 01:20 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
Updating Raspberry Pi trees pulled for -next Eric Anholt <eric@anholt.net> - 2016-06-07 00:10 +0200
Re: Updating Raspberry Pi trees pulled for -next Stephen Rothwell <sfr@canb.auug.org.au> - 2016-06-07 01:40 +0200
Re: Updating Raspberry Pi trees pulled for -next Eric Anholt <eric@anholt.net> - 2016-06-08 00:00 +0200
Re: Updating Raspberry Pi trees pulled for -next Stephen Rothwell <sfr@canb.auug.org.au> - 2016-06-08 01:20 +0200
| From | Eric Anholt <eric@anholt.net> |
|---|---|
| Date | 2016-06-07 00:10 +0200 |
| Subject | Updating Raspberry Pi trees pulled for -next |
| Message-ID | <rHaSB-2px-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
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!
[toc] | [next] | [standalone]
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2016-06-07 01:40 +0200 |
| Message-ID | <rHchI-3b1-15@gated-at.bofh.it> |
| In reply to | #1415511 |
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
[toc] | [prev] | [next] | [standalone]
| From | Eric Anholt <eric@anholt.net> |
|---|---|
| Date | 2016-06-08 00:00 +0200 |
| Message-ID | <rHxcu-85W-39@gated-at.bofh.it> |
| In reply to | #1415581 |
[Multipart message — attachments visible in raw view] — view raw
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!
[toc] | [prev] | [next] | [standalone]
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2016-06-08 01:20 +0200 |
| Message-ID | <rHyrU-Ac-11@gated-at.bofh.it> |
| In reply to | #1416670 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web