All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Dave Airlie <airlied@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: -next mostly closed, what have I missed?
Date: Wed, 17 Sep 2014 11:53:13 +0200	[thread overview]
Message-ID: <54195A09.3070504@vodafone.de> (raw)
In-Reply-To: <CAPM=9tzi=wq_G+Mk4bLBx6jst1pWWVy92zNyw5bGC6UNgmZK0w@mail.gmail.com>

I have a whole bunch of patches for radeon in the pipeline, but I'm 
perfectly fine with waiting for 3.19 with them.

Fixes for 3.18 are also already starting to stash up, so Alex will 
probably have a pull with fixes for your drm-next branch by the end of 
the week.

Regards,
Christian.

Am 17.09.2014 um 02:59 schrieb Dave Airlie:
> 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?
> Dave.
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-09-17  9:53 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
2014-09-17  9:57   ` Dave Airlie
2014-09-17  9:53 ` Christian König [this message]
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=54195A09.3070504@vodafone.de \
    --to=deathsimple@vodafone.de \
    --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.