All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✓ Fi.CI.BAT: success for series starting with [CI,1/2]  drm/i915: Combine write_domain flushes to a single function
Date: Wed, 12 Apr 2017 12:43:04 +0100	[thread overview]
Message-ID: <20170412114304.GC12532@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20170412112921.21475.4762@emeril.freedesktop.org>

On Wed, Apr 12, 2017 at 11:29:21AM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: series starting with [CI,1/2] drm/i915: Combine write_domain flushes to a single function
> URL   : https://patchwork.freedesktop.org/series/22921/
> State : success
> 
> == Summary ==
> 
> Series 22921v1 Series without cover letter
> https://patchwork.freedesktop.org/api/1.0/series/22921/revisions/1/mbox/
> 
> Test gem_exec_flush:
>         Subgroup basic-batch-kernel-default-uc:
>                 pass       -> FAIL       (fi-snb-2600) fdo#100007
> Test gem_exec_suspend:
>         Subgroup basic-s4-devices:
>                 pass       -> DMESG-WARN (fi-kbl-7560u) fdo#100125
> 
> fdo#100007 https://bugs.freedesktop.org/show_bug.cgi?id=100007
> fdo#100125 https://bugs.freedesktop.org/show_bug.cgi?id=100125

And now I can fix userspace to avoid the coherency trap.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-04-12 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 11:01 [CI 1/2] drm/i915: Combine write_domain flushes to a single function Chris Wilson
2017-04-12 11:01 ` [CI 2/2] drm/i915: Treat WC a separate cache domain Chris Wilson
2017-04-12 11:29 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915: Combine write_domain flushes to a single function Patchwork
2017-04-12 11:43   ` Chris Wilson [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=20170412114304.GC12532@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --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.