From: Patchwork <patchwork@emeril.freedesktop.org>
To: fei.yang@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: avoid concurrent writes to aux_inv (rev5)
Date: Fri, 04 Mar 2022 23:12:40 -0000 [thread overview]
Message-ID: <164643556079.21355.3537205126100172428@emeril.freedesktop.org> (raw)
In-Reply-To: <20220304221407.2416898-1-fei.yang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
== Series Details ==
Series: drm/i915: avoid concurrent writes to aux_inv (rev5)
URL : https://patchwork.freedesktop.org/series/100772/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11330 -> Patchwork_22492
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22492/index.html
Participating hosts (46 -> 41)
------------------------------
Additional (1): fi-glk-dsi
Missing (6): fi-kbl-soraka shard-tglu fi-bsw-cyan fi-icl-u2 fi-pnv-d510 fi-bdw-samus
Changes
-------
No changes found
Build changes
-------------
* IGT: IGT_6364 -> None
* Linux: CI_DRM_11330 -> Patchwork_22492
CI-20190529: 20190529
CI_DRM_11330: 68d8cd94c6eaa94aa6bae2e92efbd488523a1a1b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6364: 3523fe577bc22e6512a8de7e60175c8f46cf61d2 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22492: eb286fbe8a6ed532c821b6da358f0b1fa8af7291 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
eb286fbe8a6e drm/i915: avoid concurrent writes to aux_inv
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22492/index.html
[-- Attachment #2: Type: text/html, Size: 1858 bytes --]
next prev parent reply other threads:[~2022-03-04 23:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 22:14 [PATCH] drm/i915: avoid concurrent writes to aux_inv fei.yang
2022-03-04 22:14 ` [Intel-gfx] " fei.yang
2022-03-04 22:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: avoid concurrent writes to aux_inv (rev5) Patchwork
2022-03-04 22:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-04 23:12 ` Patchwork [this message]
2022-03-05 9:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-16 3:22 ` Summers, Stuart
2022-03-16 5:58 ` Yang, Fei
2022-03-16 4:43 ` [PATCH] drm/i915: avoid concurrent writes to aux_inv Summers, Stuart
2022-03-16 4:43 ` [Intel-gfx] " Summers, Stuart
2022-03-16 5:54 ` Yang, Fei
2022-03-16 5:54 ` [Intel-gfx] " Yang, Fei
2022-03-16 7:19 ` Yang, Fei
2022-03-16 7:19 ` [Intel-gfx] " Yang, Fei
2022-03-16 10:03 ` Tvrtko Ursulin
2022-03-16 18:25 ` Yang, Fei
2022-03-16 18:25 ` Yang, Fei
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=164643556079.21355.3537205126100172428@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=fei.yang@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 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.