All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: David Airlie <airlied@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Duncan Laurie <dlaurie@chromium.org>
Subject: Re: Regression on Chromebook Pixel 2015 due to i915 fastboot always-on
Date: Thu, 19 Nov 2015 17:44:23 +0200	[thread overview]
Message-ID: <87k2pet2nc.fsf@intel.com> (raw)
In-Reply-To: <1251506882.13386883.1447879805695.JavaMail.zimbra@redhat.com>

On Wed, 18 Nov 2015, David Airlie <airlied@redhat.com> wrote:
> I'm assuming I'll get a pull request from Jani by the end of the week,
> and I'll pass it on to you as per normal, but it might be good if he
> could accelerate that.

Done. http://mid.gmane.org/87vb8yt4a2.fsf@intel.com

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: David Airlie <airlied@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Olof Johansson <olof@lixom.net>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Duncan Laurie <dlaurie@chromium.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression on Chromebook Pixel 2015 due to i915 fastboot always-on
Date: Thu, 19 Nov 2015 17:44:23 +0200	[thread overview]
Message-ID: <87k2pet2nc.fsf@intel.com> (raw)
In-Reply-To: <1251506882.13386883.1447879805695.JavaMail.zimbra@redhat.com>

On Wed, 18 Nov 2015, David Airlie <airlied@redhat.com> wrote:
> I'm assuming I'll get a pull request from Jani by the end of the week,
> and I'll pass it on to you as per normal, but it might be good if he
> could accelerate that.

Done. http://mid.gmane.org/87vb8yt4a2.fsf@intel.com

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2015-11-19 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOesGMgvEO7-AMQ9KTWMkwSYtttJRZEhC0WET=EbR8CSU=ySkw@mail.gmail.com>
     [not found] ` <564AEC67.8020201@linux.intel.com>
     [not found]   ` <87wpthdky8.fsf@intel.com>
     [not found]     ` <CAOesGMi+-WRXJgSoWDLY_pQwEPa_c-aztDwjWaqravU2gUXUbA@mail.gmail.com>
     [not found]       ` <CA+55aFxb_mcwHi=V9=ar8VYRNGUeXi=5CsdaTGhkLxrVwGx07A@mail.gmail.com>
2015-11-17 20:35         ` Regression on Chromebook Pixel 2015 due to i915 fastboot always-on Daniel Vetter
2015-11-17 20:35           ` Daniel Vetter
2015-11-18  8:29           ` Jani Nikula
2015-11-18  8:29             ` Jani Nikula
2015-11-18 16:18             ` Linus Torvalds
2015-11-18 16:18               ` Linus Torvalds
2015-11-18 20:50               ` David Airlie
2015-11-18 20:50                 ` David Airlie
2015-11-19 15:44                 ` Jani Nikula [this message]
2015-11-19 15:44                   ` 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=87k2pet2nc.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dlaurie@chromium.org \
    --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.