From: Dave Airlie <airlied@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PULL] topic/drm-misc
Date: Tue, 22 Sep 2015 07:40:11 +1000 [thread overview]
Message-ID: <CAPM=9twmfWh-KaGQb=Gz8CFWXVUGHkcd6y1w-tEyzphx_7F9Fg@mail.gmail.com> (raw)
In-Reply-To: <CAKMK7uFkQsEKF=NOduVnD1Ur6+D7cztN6YTy+2sdyM0uaUvqfQ@mail.gmail.com>
On 17 September 2015 at 00:45, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> On Mon, Sep 14, 2015 at 8:22 AM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> Hi Dave,
>>
>> -rc1 is out the door and here's my first pull request for drm-next. It's
>> all over:
>> - better atomic helpers for runtime pm drivers
>> - atomic fbdev
>
> David Herrmann just pointed out to me that atomic fbdev isn't actually
> in this pull. Just checked my mails and it looks like there's some
> small things pending for the kerneldoc. I'll do a separate pull for
> atomic fbdev when I'm back from xdc.
> -Daniel
This also conflicts with -rc2, which I'm not really sure I like as the
first thing I pull in.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-09-21 21:40 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 15:22 [PULL] topic/drm-misc Daniel Vetter
2015-09-16 14:45 ` Daniel Vetter
2015-09-21 21:40 ` Dave Airlie [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-10 7:16 Daniel Vetter
2016-10-27 18:53 Daniel Vetter
2016-10-24 7:21 Daniel Vetter
2016-10-13 8:28 Daniel Vetter
2016-10-11 8:03 Daniel Vetter
2016-10-05 9:29 Daniel Vetter
2016-10-03 13:39 Daniel Vetter
2016-10-04 2:48 ` Dave Airlie
2016-09-25 21:26 Daniel Vetter
2016-09-19 7:11 Daniel Vetter
2016-09-08 9:30 Jani Nikula
2016-08-31 16:48 Daniel Vetter
2016-08-23 19:53 Daniel Vetter
2016-08-12 17:18 Daniel Vetter
2016-07-28 12:30 Daniel Vetter
2016-07-22 8:10 Daniel Vetter
2016-07-14 8:32 Daniel Vetter
2016-07-11 5:55 Daniel Vetter
2016-06-22 9:21 Daniel Vetter
2016-06-22 11:13 ` Daniel Vetter
2016-06-22 11:22 ` Daniel Vetter
2016-06-14 21:48 Daniel Vetter
2016-06-15 15:16 ` Daniel Vetter
2016-06-15 15:40 ` Daniel Vetter
2016-06-07 20:00 Daniel Vetter
2016-06-01 7:29 Daniel Vetter
2016-05-18 19:53 Daniel Vetter
2016-05-17 16:49 Daniel Vetter
2016-05-12 22:28 Daniel Vetter
2016-05-08 16:35 Daniel Vetter
2016-05-04 21:25 Daniel Vetter
2016-04-29 8:13 Daniel Vetter
2016-04-21 9:31 Daniel Vetter
2016-04-01 13:11 Daniel Vetter
2016-03-22 14:48 Daniel Vetter
2016-03-09 9:56 Daniel Vetter
2016-03-14 6:47 ` Daniel Vetter
2016-02-18 19:51 Daniel Vetter
2016-02-12 13:21 Daniel Vetter
2016-02-08 10:36 Daniel Vetter
2016-01-17 16:07 Daniel Vetter
2015-12-23 12:43 Daniel Vetter
2015-12-18 16:39 Daniel Vetter
2015-12-14 9:26 Daniel Vetter
2015-12-04 10:46 Daniel Vetter
2015-11-26 8:17 Daniel Vetter
2015-10-22 19:42 Daniel Vetter
2015-10-19 13:21 Daniel Vetter
2015-10-08 7:37 Daniel Vetter
2015-09-25 12:18 Daniel Vetter
2015-09-22 9:05 Daniel Vetter
2015-09-22 9:17 ` Daniel Vetter
2015-08-13 7:59 Daniel Vetter
2015-07-28 9:03 Daniel Vetter
2015-07-23 7:27 Daniel Vetter
2015-07-13 7:22 Daniel Vetter
2015-06-22 11:50 Daniel Vetter
2015-05-28 6:40 Daniel Vetter
2015-05-19 14:23 Daniel Vetter
2015-05-06 8:24 Daniel Vetter
2015-04-15 12:06 Daniel Vetter
2015-03-31 14:29 Daniel Vetter
2015-03-31 14:31 ` Daniel Vetter
2015-03-18 10:15 Daniel Vetter
2015-03-10 9:21 Daniel Vetter
2015-02-06 7:29 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='CAPM=9twmfWh-KaGQb=Gz8CFWXVUGHkcd6y1w-tEyzphx_7F9Fg@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 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).