Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org
Subject: Re: ✓ Fi.CI.BAT: success for drm/i915: set initialised only when init_context callback is NULL (rev2)
Date: Fri, 19 May 2017 12:19:18 +0300	[thread overview]
Message-ID: <87h90hjjah.fsf@intel.com> (raw)
In-Reply-To: <20170519021109.icaylvs6kcfa5a4p@zhen-hp.sh.intel.com>

On Fri, 19 May 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2017.05.12 12:44:48 +0100, Chris Wilson wrote:
>> On Fri, May 12, 2017 at 11:34:21AM -0000, Patchwork wrote:
>> > == Series Details ==
>> > 
>> > Series: drm/i915: set initialised only when init_context callback is NULL (rev2)
>> > URL   : https://patchwork.freedesktop.org/series/24286/
>> > State : success
>> > 
>> > == Summary ==
>> > 
>> > Series 24286v2 drm/i915: set initialised only when init_context callback is NULL
>> > https://patchwork.freedesktop.org/api/1.0/series/24286/revisions/2/mbox/
>> > 
>> > Test gem_exec_suspend:
>> >         Subgroup basic-s4-devices:
>> >                 pass       -> DMESG-WARN (fi-kbl-7560u) fdo#100125
>> 
>> Thanks for the patch and pushed.
>
> Could this be picked to -fixes? It should be in 4.12 and apply for
> -stable kernel too I think.

Argh, you asked this to be picked up on irc, so I did. But you only
mentioned 4.12 and nothing about stable backports, so it doesn't have
cc: stable now. Is this needed for stable?!

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-05-19  9:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 10:07 [PATCH] drm/i915: set initialised only when init_context callback is NULL Chuanxiao Dong
2017-05-11 11:00 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-05-12  9:49 ` [PATCH] " Chris Wilson
2017-05-12 10:11   ` Chris Wilson
2017-05-12 10:50     ` Dong, Chuanxiao
2017-05-12 10:11 ` [PATCH v2] " Chris Wilson
2017-05-12 11:15   ` Dong, Chuanxiao
2017-05-12 11:34 ` ✓ Fi.CI.BAT: success for drm/i915: set initialised only when init_context callback is NULL (rev2) Patchwork
2017-05-12 11:44   ` Chris Wilson
2017-05-19  2:11     ` Zhenyu Wang
2017-05-19  9:19       ` 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=87h90hjjah.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=zhenyuw@linux.intel.com \
    /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