From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: Updating Raspberry Pi trees pulled for -next
Date: Wed, 8 Jun 2016 09:10:27 +1000 [thread overview]
Message-ID: <20160608091027.4e7d792e@canb.auug.org.au> (raw)
In-Reply-To: <8737oo64ud.fsf@eliezer.anholt.net>
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
prev parent reply other threads:[~2016-06-07 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 22:08 Updating Raspberry Pi trees pulled for -next Eric Anholt
2016-06-06 23:39 ` Stephen Rothwell
2016-06-07 21:56 ` Eric Anholt
2016-06-07 23:10 ` Stephen Rothwell [this message]
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=20160608091027.4e7d792e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).