All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: -next trees
Date: Thu, 29 Sep 2016 11:47:12 +0200	[thread overview]
Message-ID: <20160929094712.GK25432@dvetter-linux.ger.corp.intel.com> (raw)
In-Reply-To: <CADnq5_OWkG3mCYrwoGyB8UES+jbH5oYZ1T0truqPy5rovKCEyg@mail.gmail.com>

On Wed, Sep 28, 2016 at 05:07:04PM -0400, Alex Deucher wrote:
> On Tue, Sep 27, 2016 at 11:31 PM, Dave Airlie <airlied@gmail.com> wrote:
> > Hey all,
> >
> > Back from a week off, I've hoovered up everything and backmerged -rc8 on top.
> >
> > If I've missed anything please let me know, I haven't seen next trees
> > for exynos or nouveau, as possibly a few others, but those are the
> > main two I noticed.
> 
> Just one last set of bug fixes I sent out a few minutes ago.

I realized that I've forgotten the generic pipe crc work from Tomeu. One
more -misc pull for that I guess.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-09-29  9:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28  3:31 -next trees Dave Airlie
2016-09-28 21:07 ` Alex Deucher
2016-09-29  9:47   ` Daniel Vetter [this message]
2016-09-29 16:23 ` Thierry Reding
  -- strict thread matches above, loose matches on Subject: below --
2012-09-13  1:44 Dave Airlie
2012-09-13 22:10 ` Alex Deucher
2012-09-17 16:25 ` Rob Clark
2012-09-22  9:43 ` Paul Menzel
2012-09-23  4:34 ` Ian Pilcher
2012-09-24 14:34   ` Adam Jackson
2012-09-25 18:47     ` Ian Pilcher
2012-09-26 17:00       ` Adam Jackson
2012-09-26 21:04         ` Ian Pilcher
2012-09-27 14:42           ` Daniel Vetter

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=20160929094712.GK25432@dvetter-linux.ger.corp.intel.com \
    --to=daniel@ffwll.ch \
    --cc=alexdeucher@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.