From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PULL] drm-misc-next-fixes, take 2
Date: Fri, 17 Feb 2017 10:15:06 +0200 [thread overview]
Message-ID: <87tw7tkzcl.fsf@intel.com> (raw)
In-Reply-To: <CAPM=9tzn3yzpjSUW6T751+4-uJroyvNQLwwH-4wR+wnk7_skHg@mail.gmail.com>
On Fri, 17 Feb 2017, Dave Airlie <airlied@gmail.com> wrote:
> On 16 February 2017 at 19:49, Jani Nikula <jani.nikula@intel.com> wrote:
>>
>> Hi Dave, this one superseeds [1]. Better to flush out the single uapi
>> fix for v4.11 now so it's not forgotten.
>
> Looks like I had already pulled, I just reverted Maarten's patch on
> top of drm-next.
Okay, thanks. Cc: Maarten FYI.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-02-17 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 9:49 [PULL] drm-misc-next-fixes, take 2 Jani Nikula
2017-02-17 2:39 ` Dave Airlie
2017-02-17 8:15 ` Jani Nikula [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=87tw7tkzcl.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=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 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.