From: Eric Anholt <eric@anholt.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Updating Raspberry Pi trees pulled for -next
Date: Mon, 06 Jun 2016 15:08:26 -0700 [thread overview]
Message-ID: <87wpm22co5.fsf@eliezer.anholt.net> (raw)
[-- 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 --]
next reply other threads:[~2016-06-06 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 22:08 Eric Anholt [this message]
2016-06-06 23:39 ` Updating Raspberry Pi trees pulled for -next Stephen Rothwell
2016-06-07 21:56 ` Eric Anholt
2016-06-07 23:10 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpm22co5.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=swarren@wwwdotorg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox