== Series Details ==
Series: bitops: Always inline sign extension helpers
URL : https://patchwork.freedesktop.org/series/74108/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8036_full -> Patchwork_16774_full
Summary
---
On Sun, Mar 1, 2020 at 2:49 PM Nicolas Dufresne wrote:
>
> Hi Jason,
>
> I personally think the suggestion are still a relatively good
> brainstorm data for those implicated. Of course, those not implicated
> in the CI scripting itself, I'd say just keep in mind that nothing is
> black and white a
== Series Details ==
Series: drm/i915/dp: Add dpcd link_rate quirk for Apple 15" MBP 2017
URL : https://patchwork.freedesktop.org/series/74100/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8035_full -> Patchwork_16772_full
== Series Details ==
Series: series starting with [CI,1/2] drm/i915/huc: update TGL HuC to v7.0.12
URL : https://patchwork.freedesktop.org/series/74099/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8035_full -> Patchwork_16771_full
On Sun, 01 Mar 2020 22:22:25 +
Chris Wilson wrote:
> > I'm curious to why we need it to be anonymous. Why not allow them to be
> > visible from the tracing directory. This could allow for easier
> > debugging. Note, the trace instances have ref counters thus they can't
> > be removed if somet
== Series Details ==
Series: drm/i915/hotplug: Use phy to get the hpd_pin instead of the port (rev5)
URL : https://patchwork.freedesktop.org/series/72747/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8035_full -> Patchwork_16770_full
==
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/virtio/virtgpu_object.c
between commit:
6be7e0733548 ("drm/virtio: fix mmap page attributes")
from the drm-misc-fixes tree and commit:
18b39fb975b7 ("drm/virtio: add virtio_gpu_is_shmem helper")
from th
Quoting Steven Rostedt (2020-03-01 18:18:16)
> On Sun, 1 Mar 2020 15:52:47 +
> Chris Wilson wrote:
>
> > To facilitate construction of per-client event ringbuffers, in
> > particular for a per-client debug and error report log, it would be
> > extremely useful to create an anonymous file tha
Stan, I have addressed and reported the issue.
From: Lisovskiy, Stanislav
Sent: Sunday, March 1, 2020 6:12 PM
To: intel-gfx@lists.freedesktop.org; Peres, Martin ;
Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Use intel_plane_data_rate for
min_cdclk calculation (rev6)
== Series Details ==
Series: drm/i915: Use intel_plane_data_rate for min_cdclk calculation (rev6)
URL : https://patchwork.freedesktop.org/series/73718/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8020_full -> Patchwork_16737_full
=
== Series Details ==
Series: drm/i915: Use intel_plane_data_rate for min_cdclk calculation (rev6)
URL : https://patchwork.freedesktop.org/series/73718/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8020_full -> Patchwork_16737_full
=
I don't think we need to worry so much about the cost of CI that we need to
micro-optimize to to get the minimal number of CI runs. We especially
shouldn't if it begins to impact coffee quality, people's ability to merge
patches in a timely manner, or visibility into what went wrong when CI
fai
== Series Details ==
Series: drm/i915/display: nuke skl workaround for pre-production hw (rev3)
URL : https://patchwork.freedesktop.org/series/71230/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8034_full -> Patchwork_16769_full
===
One idea for Marge-bot (don't know if you already do this):
Rust-lang has their bot (bors) automatically group together a few merge
requests into a single merge commit, which it then tests, then, then the
tests pass, it merges. This could help reduce CI runs to once a day (or
some other rate). If t
== Series Details ==
Series: series starting with [1/4] drm/i915: Don't check uv_wm in
skl_plane_wm_equals()
URL : https://patchwork.freedesktop.org/series/74092/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8033_full -> Patchwork_16768_full
=
On Sun, 1 Mar 2020 15:52:47 +
Chris Wilson wrote:
> To facilitate construction of per-client event ringbuffers, in
> particular for a per-client debug and error report log, it would be
> extremely useful to create an anonymous file that can be handed to
> userspace so that it can see its and
Quoting Lionel Landwerlin (2020-03-01 16:27:24)
> On 01/03/2020 17:52, Chris Wilson wrote:
> > Rather than put sensitive, and often voluminous, user details into a
> > global dmesg, report the error and debug messages directly back to the
> > user via the kernel tracing mechanism.
>
>
> Sounds re
On 01/03/2020 17:52, Chris Wilson wrote:
Rather than put sensitive, and often voluminous, user details into a
global dmesg, report the error and debug messages directly back to the
user via the kernel tracing mechanism.
Sounds really nice. Don't you want the existing global tracing to be the
== Series Details ==
Series: series starting with [1/2] trace: Export anonymous tracing
URL : https://patchwork.freedesktop.org/series/74117/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8037 -> Patchwork_16775
Summary
---
Hi,
The IGT issue here is unrelated to intel_plane_data_rate change. Looks pretty
weird though :)
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
From: Patchwork
Sent: Saturday, February 29, 202
== Series Details ==
Series: series starting with [1/2] trace: Export anonymous tracing
URL : https://patchwork.freedesktop.org/series/74117/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
0385cbf331ee trace: Export anonymous tracing
26fbc3a0c7c8 RFC drm/i915: Export per-client
Rather than put sensitive, and often voluminous, user details into a
global dmesg, report the error and debug messages directly back to the
user via the kernel tracing mechanism.
Signed-off-by: Chris Wilson
Cc: Steven Rostedt (VMware)
---
drivers/gpu/drm/i915/gem/i915_gem_context.c | 104
To facilitate construction of per-client event ringbuffers, in
particular for a per-client debug and error report log, it would be
extremely useful to create an anonymous file that can be handed to
userspace so that it can see its and only its events. trace already
provides a means of encapsulating
== Series Details ==
Series: drm/i915: Fix 90/270 degree rotated RGB565 src coord checks (rev3)
URL : https://patchwork.freedesktop.org/series/59956/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8032_full -> Patchwork_16766_full
===
On 2020-02-29 8:46 p.m., Nicolas Dufresne wrote:
> Le samedi 29 février 2020 à 19:14 +0100, Timur Kristóf a écrit :
>>
>> 1. I think we should completely disable running the CI on MRs which are
>> marked WIP. Speaking from personal experience, I usually make a lot of
>> changes to my MRs before the
== Series Details ==
Series: drm/i915: Clean up DPLL output/refclock tracking (rev2)
URL : https://patchwork.freedesktop.org/series/73977/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8032_full -> Patchwork_16764_full
Summ
== Series Details ==
Series: drm/i915/selftests: Fix return in assert_mmap_offset()
URL : https://patchwork.freedesktop.org/series/74081/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8032_full -> Patchwork_16763_full
Summa
== Series Details ==
Series: series starting with [1/7] drm/i915/gt: Expose engine properties via
sysfs
URL : https://patchwork.freedesktop.org/series/74080/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8032_full -> Patchwork_16762_full
==
== Series Details ==
Series: drm/i915: Some upside-down panel handling fixes
URL : https://patchwork.freedesktop.org/series/74076/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8030_full -> Patchwork_16761_full
Summary
29 matches
Mail list logo
