Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Lucas De Marchi" <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ Xe.CI.BAT: success for drm/i915: DRAM type logging
Date: Tue, 25 Mar 2025 03:16:19 -0000	[thread overview]
Message-ID: <174287257943.75914.11211013689482877830@18a75f3d1eae> (raw)
In-Reply-To: <20250324-dram-type-v1-0-bf60ef33ac01@intel.com>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

== Series Details ==

Series: drm/i915: DRAM type logging
URL   : https://patchwork.freedesktop.org/series/146700/
State : success

== Summary ==

CI Bug Log - changes from xe-2844-9a42bdcde0f77b2c1e947e283cc3b267b1ce2056_BAT -> xe-pw-146700v1_BAT
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  

Participating hosts (10 -> 9)
------------------------------

  Missing    (1): bat-adlp-vm 


Changes
-------

  No changes found


Build changes
-------------

  * Linux: xe-2844-9a42bdcde0f77b2c1e947e283cc3b267b1ce2056 -> xe-pw-146700v1

  IGT_8281: 18c445bea641c03b637d7ed5bc3bd120b5d83b2a @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  xe-2844-9a42bdcde0f77b2c1e947e283cc3b267b1ce2056: 9a42bdcde0f77b2c1e947e283cc3b267b1ce2056
  xe-pw-146700v1: 146700v1

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146700v1/index.html

[-- Attachment #2: Type: text/html, Size: 1483 bytes --]

  parent reply	other threads:[~2025-03-25  3:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25  2:28 [PATCH 0/2] drm/i915: DRAM type logging Lucas De Marchi
2025-03-25  2:28 ` [PATCH 1/2] drm/i915/dram: Add missing INTEL_DRAM str conversions Lucas De Marchi
2025-03-28 22:25   ` Matt Roper
2025-03-25  2:28 ` [PATCH 2/2] drm/i915/dram: Consolidate logging of DRAM type Lucas De Marchi
2025-03-28 22:29   ` Matt Roper
2025-03-25  2:34 ` ✓ CI.Patch_applied: success for drm/i915: DRAM type logging Patchwork
2025-03-25  2:34 ` ✓ CI.checkpatch: " Patchwork
2025-03-25  2:36 ` ✓ CI.KUnit: " Patchwork
2025-03-25  2:52 ` ✓ CI.Build: " Patchwork
2025-03-25  2:54 ` ✓ CI.Hooks: " Patchwork
2025-03-25  2:56 ` ✗ CI.checksparse: warning " Patchwork
2025-03-25  3:16 ` Patchwork [this message]
2025-03-31 15:18 ` [PATCH 0/2] " Lucas De Marchi

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=174287257943.75914.11211013689482877830@18a75f3d1eae \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@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