From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for drm/i915/guc: Drop comment on fwif autogeneration
Date: Tue, 6 Dec 2016 06:41:40 +0100 [thread overview]
Message-ID: <20161206054139.GC7252@ahiler-desk.igk.intel.com> (raw)
In-Reply-To: <20161205185901.20865.32443@emeril.freedesktop.org>
On Mon, Dec 05, 2016 at 06:59:01PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: Drop comment on fwif autogeneration
> URL : https://patchwork.freedesktop.org/series/16373/
> State : warning
>
> == Summary ==
>
> Series 16373v1 drm/i915/guc: Drop comment on fwif autogeneration
> https://patchwork.freedesktop.org/api/1.0/series/16373/revisions/1/mbox/
>
> Test gem_busy:
> Subgroup basic-hang-default:
> fail -> PASS (fi-hsw-4770r)
The cange is only a comment removal. Could not affect the pass.
> Test kms_pipe_crc_basic:
> Subgroup suspend-read-crc-pipe-a:
> pass -> DMESG-WARN (fi-skl-6770hq)
>
[ 408.780897] [drm:skl_set_cdclk [i915]] *ERROR* failed to inform PCU about cdclk change
https://bugs.freedesktop.org/show_bug.cgi?id=97929
>
> a947529bb652fdcf50e8c0e8ee5102b737bae23e drm-tip: 2016y-12m-05d-14h-27m-06s UTC integration manifest
> abb5dbd drm/i915/guc: Drop comment on fwif autogeneration
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3196/
--
Cheers,
Arek
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-06 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 16:04 [PATCH] drm/i915/guc: Drop comment on fwif autogeneration Arkadiusz Hiler
2016-12-05 18:59 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-12-06 5:41 ` Arkadiusz Hiler [this message]
2016-12-07 7:14 ` Tvrtko Ursulin
2016-12-05 21:37 ` [PATCH] " Jeff McGee
2016-12-05 23:59 ` Srivatsa, Anusha
2016-12-06 5:37 ` Arkadiusz Hiler
2016-12-06 17:31 ` Srivatsa, Anusha
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=20161206054139.GC7252@ahiler-desk.igk.intel.com \
--to=arkadiusz.hiler@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox