From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm fixes for 4.8
Date: Mon, 19 Sep 2016 12:19:27 +0300 [thread overview]
Message-ID: <874m5cnt5s.fsf@intel.com> (raw)
In-Reply-To: <877fa8ntle.fsf@intel.com>
On Mon, 19 Sep 2016, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 19 Sep 2016, Dave Airlie <airlied@gmail.com> wrote:
>> Hi Linus,
>>
>> One important drm 32/64 ABI fix came in so I'll dequeue what I have, the rest is
>> just exynos runtime pm fixes, but the net removal of code seems like a
>> win to me.
>>
>> I'm going to be sporadic this week due to school holidays, so if anything urgent
>> turns up, Daniel will take care of it.
>
> Hmm, missing my pull req [1]?
I failed to see Dave's other pull request. Sorry for the noise.
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
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm fixes for 4.8
Date: Mon, 19 Sep 2016 12:19:27 +0300 [thread overview]
Message-ID: <874m5cnt5s.fsf@intel.com> (raw)
In-Reply-To: <877fa8ntle.fsf@intel.com>
On Mon, 19 Sep 2016, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 19 Sep 2016, Dave Airlie <airlied@gmail.com> wrote:
>> Hi Linus,
>>
>> One important drm 32/64 ABI fix came in so I'll dequeue what I have, the rest is
>> just exynos runtime pm fixes, but the net removal of code seems like a
>> win to me.
>>
>> I'm going to be sporadic this week due to school holidays, so if anything urgent
>> turns up, Daniel will take care of it.
>
> Hmm, missing my pull req [1]?
I failed to see Dave's other pull request. Sorry for the noise.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-09-19 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 7:42 [git pull] drm fixes for 4.8 Dave Airlie
2016-09-19 7:42 ` Dave Airlie
2016-09-19 9:10 ` Jani Nikula
2016-09-19 9:10 ` Jani Nikula
2016-09-19 9:19 ` Jani Nikula [this message]
2016-09-19 9:19 ` Jani Nikula
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=874m5cnt5s.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.