From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Francisco Jerez" <currojerez@riseup.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [PATCHv2.99,01/11] PM: QoS: Add CPU_SCALING_RESPONSE global PM QoS limit.
Date: Tue, 28 Apr 2020 03:32:46 -0000 [thread overview]
Message-ID: <158804476661.17773.16186729538100888549@emeril.freedesktop.org> (raw)
In-Reply-To: <20200428032258.2518-1-currojerez@riseup.net>
== Series Details ==
Series: series starting with [PATCHv2.99,01/11] PM: QoS: Add CPU_SCALING_RESPONSE global PM QoS limit.
URL : https://patchwork.freedesktop.org/series/76576/
State : failure
== Summary ==
Applying: PM: QoS: Add CPU_SCALING_RESPONSE global PM QoS limit.
Applying: drm/i915: Adjust PM QoS scaling response frequency based on GPU load.
error: sha1 information is lacking or useless (drivers/gpu/drm/i915/gt/intel_lrc.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 drm/i915: Adjust PM QoS scaling response frequency based on GPU load.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-28 3:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 3:22 [RFC] GPU-bound energy efficiency improvements for the intel_pstate driver (v2.99) Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 01/11] PM: QoS: Add CPU_SCALING_RESPONSE global PM QoS limit Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 02/11] drm/i915: Adjust PM QoS scaling response frequency based on GPU load Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 03/11] OPTIONAL: drm/i915: Expose PM QoS control parameters via debugfs Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 04/11] cpufreq: Define ADAPTIVE frequency governor policy Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 05/11] cpufreq: intel_pstate: Reorder intel_pstate_clear_update_util_hook() and intel_pstate_set_update_util_hook() Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 06/11] cpufreq: intel_pstate: Call intel_pstate_set_update_util_hook() once from the setpolicy hook Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 07/11] cpufreq: intel_pstate: Implement VLP controller statistics and target range calculation Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 08/11] cpufreq: intel_pstate: Implement VLP controller for HWP parts Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 09/11] cpufreq: intel_pstate: Enable VLP controller based on ACPI FADT profile and CPUID Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 10/11] OPTIONAL: cpufreq: intel_pstate: Add tracing of VLP controller status Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:22 ` [PATCHv2.99 11/11] OPTIONAL: cpufreq: intel_pstate: Expose VLP controller parameters via debugfs Francisco Jerez
2020-04-28 3:22 ` [Intel-gfx] " Francisco Jerez
2020-04-28 3:32 ` Patchwork [this message]
2020-05-11 10:57 ` [RFC] GPU-bound energy efficiency improvements for the intel_pstate driver (v2.99) Peter Zijlstra
2020-05-11 10:57 ` [Intel-gfx] " Peter Zijlstra
2020-05-11 21:01 ` Francisco Jerez
2020-05-11 21:01 ` [Intel-gfx] " Francisco Jerez
2020-05-14 10:26 ` Rafael J. Wysocki
2020-05-14 10:26 ` [Intel-gfx] " Rafael J. Wysocki
2020-05-15 0:48 ` Francisco Jerez
2020-05-15 0:48 ` [Intel-gfx] " Francisco Jerez
2020-05-14 11:50 ` Valentin Schneider
2020-05-14 11:50 ` [Intel-gfx] " Valentin Schneider
2020-05-15 0:48 ` Francisco Jerez
2020-05-15 0:48 ` [Intel-gfx] " Francisco Jerez
2020-05-15 18:09 ` Valentin Schneider
2020-05-15 18:09 ` [Intel-gfx] " Valentin Schneider
2020-05-28 9:29 ` Lukasz Luba
2020-05-28 9:29 ` [Intel-gfx] " Lukasz Luba
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=158804476661.17773.16186729538100888549@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=currojerez@riseup.net \
--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.