From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Riana Tauro" <riana.tauro@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.Patch_applied: success for PMU Support for per-engine-class activity
Date: Mon, 06 Jan 2025 08:28:48 -0000 [thread overview]
Message-ID: <173615212800.98986.2371546783115763616@b555e5b46a47> (raw)
In-Reply-To: <20250106075600.852080-1-riana.tauro@intel.com>
== Series Details ==
Series: PMU Support for per-engine-class activity
URL : https://patchwork.freedesktop.org/series/143138/
State : success
== Summary ==
=== Applying kernel patches on branch 'drm-tip' with base: ===
Base commit: 03abdf4d5729 drm-tip: 2025y-01m-06d-08h-25m-27s UTC integration manifest
=== git am output follows ===
.git/rebase-apply/patch:751: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
.git/rebase-apply/patch:498: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Applying: drm/xe/pmu: Enable PMU interface
Applying: drm/xe: Add locks in gtidle code
Applying: drm/xe/pmu: Add GT C6 events
Applying: drm/xe/pmu: Add GT frequency events
Applying: drm/xe/xe_pmu: add fixes for base PMU
Applying: drm/xe: Add per-engine-class activity support
Applying: drm/xe/trace: Add trace for engine activity
Applying: drm/xe/guc: Expose engine activity only for supported GuC version
Applying: drm/xe/pmu: Add PMU support for per-engine-class activity
Applying: drm/xe/guc: Bump minimum required GuC version to v70.36.0
next prev parent reply other threads:[~2025-01-06 8:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 7:55 [PATCH v3 00/10] PMU Support for per-engine-class activity Riana Tauro
2025-01-06 7:55 ` [PATCH v3 01/10] [DO NOT REVIEW] drm/xe/pmu: Enable PMU interface Riana Tauro
2025-01-06 7:55 ` [PATCH v3 02/10] [DO NOT REVIEW] drm/xe: Add locks in gtidle code Riana Tauro
2025-01-06 7:55 ` [PATCH v3 03/10] [DO NOT REVIEW] drm/xe/pmu: Add GT C6 events Riana Tauro
2025-01-06 7:55 ` [PATCH v3 04/10] [DO NOT REVIEW] drm/xe/pmu: Add GT frequency events Riana Tauro
2025-01-06 7:55 ` [PATCH v3 05/10] [DO NOT REVIEW] drm/xe/xe_pmu: add fixes for base PMU Riana Tauro
2025-01-06 7:55 ` [PATCH v3 06/10] drm/xe: Add per-engine-class activity support Riana Tauro
2025-01-06 7:55 ` [PATCH v3 07/10] drm/xe/trace: Add trace for engine activity Riana Tauro
2025-01-16 23:08 ` Umesh Nerlige Ramappa
2025-01-06 7:55 ` [PATCH v3 08/10] drm/xe/guc: Expose engine activity only for supported GuC version Riana Tauro
2025-01-16 23:10 ` Umesh Nerlige Ramappa
2025-01-27 10:05 ` Riana Tauro
2025-01-06 7:55 ` [PATCH v3 09/10] drm/xe/pmu: Add PMU support for per-engine-class activity Riana Tauro
2025-01-14 0:57 ` Umesh Nerlige Ramappa
2025-01-17 1:18 ` Umesh Nerlige Ramappa
2025-01-17 13:26 ` Riana Tauro
2025-01-06 7:55 ` [PATCH v3 10/10] drm/xe/guc: Bump minimum required GuC version to v70.36.0 Riana Tauro
2025-01-06 8:28 ` Patchwork [this message]
2025-01-06 8:29 ` ✗ CI.checkpatch: warning for PMU Support for per-engine-class activity Patchwork
2025-01-06 8:30 ` ✓ CI.KUnit: success " Patchwork
2025-01-06 8:48 ` ✓ CI.Build: " Patchwork
2025-01-06 8:50 ` ✗ CI.Hooks: failure " Patchwork
2025-01-06 8:52 ` ✓ CI.checksparse: success " Patchwork
2025-01-06 9:18 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-06 17:10 ` ✗ Xe.CI.Full: failure " Patchwork
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=173615212800.98986.2371546783115763616@b555e5b46a47 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=riana.tauro@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