From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: -next mostly closed, what have I missed?
Date: Wed, 17 Sep 2014 12:45:36 +0300 [thread overview]
Message-ID: <1722693.f0mPDKUYiU@avalon> (raw)
In-Reply-To: <CAPM=9tzi=wq_G+Mk4bLBx6jst1pWWVy92zNyw5bGC6UNgmZK0w@mail.gmail.com>
Hi Dave,
On Wednesday 17 September 2014 10:59:42 Dave Airlie wrote:
> Okay so I'm pretty sure I'm close to not taking anything major for next,
>
> I'm not sure I've gotten an exynos tree yet, so hopefully that appears
> before -rc6,
>
> Please continue to send fixes for -next pulls, and I'm kinda open to
> new hw support depending on how intrusive it is to other code.
>
> Now we have a strange new time of a few weeks where maybe we should go
> fix some regressions or something!
>
> any other trees I've missed?
Yes, you seem to have missed "[GIT PULL FOR v3.18] Renesas DRM changes".
The following changes since commit 98faa78ce7f1f986e11e7805d31b409782a6d2d4:
Merge tag 'topic/drm-header-rework-2014-09-12' of
git://anongit.freedesktop.org/drm-intel into drm-next (2014-09-13 07:01:49
+1000)
are available in the git repository at:
git://linuxtv.org/pinchartl/fbdev.git drm/next/du
for you to fetch changes up to 96c026911890ceacee238da00a0b140ad634cc43:
drm/rcar-du: Add OF support (2014-09-15 11:55:47 +0300)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-09-17 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 0:59 -next mostly closed, what have I missed? Dave Airlie
2014-09-17 7:59 ` Joonyoung Shim
2014-09-17 9:45 ` Laurent Pinchart [this message]
2014-09-17 9:57 ` Dave Airlie
2014-09-17 9:53 ` Christian König
2014-09-17 10:02 ` Inki Dae
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=1722693.f0mPDKUYiU@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.