* ✗ Fi.CI.CHECKPATCH: warning for linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-21 0:51 linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
@ 2019-05-21 1:02 ` Patchwork
2019-05-21 15:08 ` ✗ Fi.CI.CHECKPATCH: warning for linux-next: manual merge of the drm-misc tree with Linus' tree (rev2) Patchwork
` (5 subsequent siblings)
6 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2019-05-21 1:02 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: intel-gfx
== Series Details ==
Series: linux-next: manual merge of the drm-misc tree with Linus' tree
URL : https://patchwork.freedesktop.org/series/60886/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
75ba999b2c56 linux-next: manual merge of the drm-misc tree with Linus' tree
-:15: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")'
#15:
8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
-:19: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")'
#19:
b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
-:20: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#20:
b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
-:20: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")'
#20:
b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
-:21: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")'
#21:
fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
-:62: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 5 errors, 1 warnings, 0 checks, 24 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* ✗ Fi.CI.CHECKPATCH: warning for linux-next: manual merge of the drm-misc tree with Linus' tree (rev2)
2019-05-21 0:51 linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
2019-05-21 1:02 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
@ 2019-05-21 15:08 ` Patchwork
2019-05-21 15:28 ` ✓ Fi.CI.BAT: success " Patchwork
` (4 subsequent siblings)
6 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2019-05-21 15:08 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: intel-gfx
== Series Details ==
Series: linux-next: manual merge of the drm-misc tree with Linus' tree (rev2)
URL : https://patchwork.freedesktop.org/series/60886/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9ade394d0944 linux-next: manual merge of the drm-misc tree with Linus' tree
-:15: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")'
#15:
8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
-:19: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")'
#19:
b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
-:20: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#20:
b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
-:20: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")'
#20:
b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
-:21: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")'
#21:
fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
-:62: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 5 errors, 1 warnings, 0 checks, 24 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* ✓ Fi.CI.BAT: success for linux-next: manual merge of the drm-misc tree with Linus' tree (rev2)
2019-05-21 0:51 linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
2019-05-21 1:02 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-05-21 15:08 ` ✗ Fi.CI.CHECKPATCH: warning for linux-next: manual merge of the drm-misc tree with Linus' tree (rev2) Patchwork
@ 2019-05-21 15:28 ` Patchwork
2019-05-22 8:44 ` ✗ Fi.CI.IGT: failure " Patchwork
` (3 subsequent siblings)
6 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2019-05-21 15:28 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: intel-gfx
== Series Details ==
Series: linux-next: manual merge of the drm-misc tree with Linus' tree (rev2)
URL : https://patchwork.freedesktop.org/series/60886/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6114 -> Patchwork_13056
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/
Known issues
------------
Here are the changes found in Patchwork_13056 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@gem_basic@create-fd-close:
- {fi-icl-u3}: [DMESG-WARN][1] ([fdo#107724]) -> [PASS][2] +2 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/fi-icl-u3/igt@gem_basic@create-fd-close.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/fi-icl-u3/igt@gem_basic@create-fd-close.html
* igt@i915_selftest@live_contexts:
- fi-skl-gvtdvm: [DMESG-FAIL][3] ([fdo#110235]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/fi-skl-gvtdvm/igt@i915_selftest@live_contexts.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/fi-skl-gvtdvm/igt@i915_selftest@live_contexts.html
* igt@i915_selftest@live_hangcheck:
- {fi-icl-y}: [INCOMPLETE][5] ([fdo#107713] / [fdo#108569]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/fi-icl-y/igt@i915_selftest@live_hangcheck.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/fi-icl-y/igt@i915_selftest@live_hangcheck.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#110235]: https://bugs.freedesktop.org/show_bug.cgi?id=110235
Participating hosts (53 -> 45)
------------------------------
Missing (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-bsw-n3050 fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_6114 -> Patchwork_13056
CI_DRM_6114: 8691fe536e41c852d3d420ed09b1d5f9916031e7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5000: f9961d14d76b3a0fa1296e547f7c065e2f93955c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_13056: 9ade394d094435126ce59cff5f9dd70bd0891de0 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
9ade394d0944 linux-next: manual merge of the drm-misc tree with Linus' tree
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* ✗ Fi.CI.IGT: failure for linux-next: manual merge of the drm-misc tree with Linus' tree (rev2)
2019-05-21 0:51 linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
` (2 preceding siblings ...)
2019-05-21 15:28 ` ✓ Fi.CI.BAT: success " Patchwork
@ 2019-05-22 8:44 ` Patchwork
2019-05-23 0:27 ` linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
` (2 subsequent siblings)
6 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2019-05-22 8:44 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: intel-gfx
== Series Details ==
Series: linux-next: manual merge of the drm-misc tree with Linus' tree (rev2)
URL : https://patchwork.freedesktop.org/series/60886/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6114_full -> Patchwork_13056_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_13056_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_13056_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_13056_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
- shard-hsw: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-hsw7/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-hsw1/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc:
- shard-snb: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-snb5/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-snb6/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* {igt@kms_big_fb@x-tiled-8bpp-rotate-90}:
- shard-iclb: NOTRUN -> [SKIP][5] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb6/igt@kms_big_fb@x-tiled-8bpp-rotate-90.html
* {igt@kms_cursor_crc@pipe-c-cursor-suspend}:
- shard-skl: [PASS][6] -> [INCOMPLETE][7]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl9/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl5/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
Known issues
------------
Here are the changes found in Patchwork_13056_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@bcs0-s3:
- shard-apl: [PASS][8] -> [DMESG-WARN][9] ([fdo#108566]) +3 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-apl4/igt@gem_ctx_isolation@bcs0-s3.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-apl4/igt@gem_ctx_isolation@bcs0-s3.html
* igt@gem_mocs_settings@mocs-isolation-bsd1:
- shard-kbl: [PASS][10] -> [SKIP][11] ([fdo#109271])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-kbl7/igt@gem_mocs_settings@mocs-isolation-bsd1.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-kbl4/igt@gem_mocs_settings@mocs-isolation-bsd1.html
* igt@gem_tiled_swapping@non-threaded:
- shard-iclb: [PASS][12] -> [FAIL][13] ([fdo#108686])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb7/igt@gem_tiled_swapping@non-threaded.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb5/igt@gem_tiled_swapping@non-threaded.html
- shard-hsw: [PASS][14] -> [FAIL][15] ([fdo#108686])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-hsw7/igt@gem_tiled_swapping@non-threaded.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-hsw1/igt@gem_tiled_swapping@non-threaded.html
* igt@i915_pm_rpm@gem-mmap-cpu:
- shard-skl: [PASS][16] -> [INCOMPLETE][17] ([fdo#107807])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl3/igt@i915_pm_rpm@gem-mmap-cpu.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl2/igt@i915_pm_rpm@gem-mmap-cpu.html
* igt@i915_pm_rpm@system-suspend:
- shard-skl: [PASS][18] -> [INCOMPLETE][19] ([fdo#104108] / [fdo#107807])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl5/igt@i915_pm_rpm@system-suspend.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl10/igt@i915_pm_rpm@system-suspend.html
* igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic:
- shard-glk: [PASS][20] -> [FAIL][21] ([fdo#106509] / [fdo#107409])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-glk3/igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-glk1/igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: [PASS][22] -> [FAIL][23] ([fdo#102670] / [fdo#106081])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-glk9/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-glk4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-kbl: [PASS][24] -> [FAIL][25] ([fdo#102670])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-kbl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-kbl4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible:
- shard-glk: [PASS][26] -> [FAIL][27] ([fdo#105363])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-glk4/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-glk7/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@dpms-vs-vblank-race-interruptible:
- shard-iclb: [PASS][28] -> [INCOMPLETE][29] ([fdo#107713])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb4/igt@kms_flip@dpms-vs-vblank-race-interruptible.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb7/igt@kms_flip@dpms-vs-vblank-race-interruptible.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-glk: [PASS][30] -> [FAIL][31] ([fdo#102887] / [fdo#105363])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-glk8/igt@kms_flip@flip-vs-expired-vblank.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-glk3/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_frontbuffer_tracking@fbc-farfromfence:
- shard-iclb: [PASS][32] -> [FAIL][33] ([fdo#103167])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-farfromfence.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-farfromfence.html
* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-skl: [PASS][34] -> [INCOMPLETE][35] ([fdo#104108] / [fdo#106978])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl3/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl10/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-skl: [PASS][36] -> [INCOMPLETE][37] ([fdo#104108])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl6/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl2/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [PASS][38] -> [SKIP][39] ([fdo#109441]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb8/igt@kms_psr@psr2_cursor_mmap_cpu.html
#### Possible fixes ####
* igt@gem_eio@in-flight-suspend:
- shard-apl: [FAIL][40] -> [PASS][41]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-apl7/igt@gem_eio@in-flight-suspend.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-apl2/igt@gem_eio@in-flight-suspend.html
* igt@gem_exec_flush@basic-uc-rw-default:
- shard-iclb: [INCOMPLETE][42] ([fdo#107713]) -> [PASS][43]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb7/igt@gem_exec_flush@basic-uc-rw-default.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb1/igt@gem_exec_flush@basic-uc-rw-default.html
* igt@gem_pwrite@big-gtt-forwards:
- shard-glk: [INCOMPLETE][44] ([fdo#103359] / [k.org#198133]) -> [PASS][45]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-glk5/igt@gem_pwrite@big-gtt-forwards.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-glk2/igt@gem_pwrite@big-gtt-forwards.html
* igt@i915_pm_rpm@fences:
- shard-skl: [INCOMPLETE][46] ([fdo#107807]) -> [PASS][47]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl4/igt@i915_pm_rpm@fences.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl7/igt@i915_pm_rpm@fences.html
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-skl: [INCOMPLETE][48] ([fdo#104108]) -> [PASS][49]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl2/igt@i915_suspend@fence-restore-tiled2untiled.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl2/igt@i915_suspend@fence-restore-tiled2untiled.html
* igt@kms_atomic_interruptible@universal-setplane-primary:
- shard-apl: [INCOMPLETE][50] ([fdo#103927]) -> [PASS][51] +1 similar issue
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-apl5/igt@kms_atomic_interruptible@universal-setplane-primary.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-apl4/igt@kms_atomic_interruptible@universal-setplane-primary.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [FAIL][52] ([fdo#102670]) -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_dp_dsc@basic-dsc-enable-edp:
- shard-iclb: [SKIP][54] ([fdo#109349]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb4/igt@kms_dp_dsc@basic-dsc-enable-edp.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb2/igt@kms_dp_dsc@basic-dsc-enable-edp.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt:
- shard-iclb: [FAIL][56] ([fdo#103167]) -> [PASS][57] +4 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt.html
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [FAIL][58] ([fdo#108145]) -> [PASS][59] +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl3/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl10/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][60] ([fdo#109642]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb7/igt@kms_psr2_su@frontbuffer.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb2/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][62] ([fdo#109441]) -> [PASS][63] +2 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb4/igt@kms_psr@psr2_primary_mmap_cpu.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_setmode@basic:
- shard-kbl: [FAIL][64] ([fdo#99912]) -> [PASS][65]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-kbl7/igt@kms_setmode@basic.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-kbl3/igt@kms_setmode@basic.html
* igt@kms_vblank@pipe-c-ts-continuation-suspend:
- shard-apl: [DMESG-WARN][66] ([fdo#108566]) -> [PASS][67] +6 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-apl8/igt@kms_vblank@pipe-c-ts-continuation-suspend.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-apl1/igt@kms_vblank@pipe-c-ts-continuation-suspend.html
* igt@perf@polling:
- shard-iclb: [FAIL][68] -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-iclb4/igt@perf@polling.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-iclb1/igt@perf@polling.html
#### Warnings ####
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-pwrite:
- shard-skl: [FAIL][70] ([fdo#108040]) -> [FAIL][71] ([fdo#103167])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-skl3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-pwrite.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/shard-skl5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-pwrite.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#102670]: https://bugs.freedesktop.org/show_bug.cgi?id=102670
[fdo#102887]: https://bugs.freedesktop.org/show_bug.cgi?id=102887
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#106081]: https://bugs.freedesktop.org/show_bug.cgi?id=106081
[fdo#106509]: https://bugs.freedesktop.org/show_bug.cgi?id=106509
[fdo#106978]: https://bugs.freedesktop.org/show_bug.cgi?id=106978
[fdo#107409]: https://bugs.freedesktop.org/show_bug.cgi?id=107409
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107807]: https://bugs.freedesktop.org/show_bug.cgi?id=107807
[fdo#108040]: https://bugs.freedesktop.org/show_bug.cgi?id=108040
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#108686]: https://bugs.freedesktop.org/show_bug.cgi?id=108686
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109349]: https://bugs.freedesktop.org/show_bug.cgi?id=109349
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_6114 -> Patchwork_13056
CI_DRM_6114: 8691fe536e41c852d3d420ed09b1d5f9916031e7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5000: f9961d14d76b3a0fa1296e547f7c065e2f93955c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_13056: 9ade394d094435126ce59cff5f9dd70bd0891de0 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13056/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-21 0:51 linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
` (3 preceding siblings ...)
2019-05-22 8:44 ` ✗ Fi.CI.IGT: failure " Patchwork
@ 2019-05-23 0:27 ` Stephen Rothwell
2019-05-23 8:10 ` Maxime Ripard
2019-05-23 11:53 ` Maxime Ripard
6 siblings, 0 replies; 18+ messages in thread
From: Stephen Rothwell @ 2019-05-23 0:27 UTC (permalink / raw)
To: Sean Paul
Cc: Daniel Vetter, Intel Graphics, DRI, Linux Next Mailing List,
Linux Kernel Mailing List, Rob Herring, Fabio Estevam,
Thierry Reding, Jyri Sarha, Marco Felsch
[-- Attachment #1: Type: text/plain, Size: 2872 bytes --]
Hi Sean,
On Tue, 21 May 2019 10:51:51 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
>
> Documentation/devicetree/bindings/vendor-prefixes.txt
>
> between commit:
>
> 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
>
> from Linus' tree and commits:
>
> b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
>
> from the drm-misc tree.
>
> I fixed it up (I deleted the file and added the patch below) and can
> carry the fix as necessary. This is now fixed as far as linux-next is
> concerned, but any non trivial conflicts should be mentioned to your
> upstream maintainer when your tree is submitted for merging. You may
> also want to consider cooperating with the maintainer of the conflicting
> tree to minimise any particularly complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 21 May 2019 10:48:36 +1000
> Subject: [PATCH] dt-bindings: fix up for vendor prefixes file conversion
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 83ca4816a78b..749e3c3843d0 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -287,6 +287,8 @@ patternProperties:
> description: Everest Semiconductor Co. Ltd.
> "^everspin,.*":
> description: Everspin Technologies, Inc.
> + "^evervision,.*":
> + description: Evervision Electronics Co. Ltd.
> "^exar,.*":
> description: Exar Corporation
> "^excito,.*":
> @@ -851,6 +853,8 @@ patternProperties:
> description: Shenzhen Techstar Electronics Co., Ltd.
> "^terasic,.*":
> description: Terasic Inc.
> + "^tfc,.*":
> + description: Three Five Corp
> "^thine,.*":
> description: THine Electronics, Inc.
> "^ti,.*":
> @@ -925,6 +929,8 @@ patternProperties:
> description: Voipac Technologies s.r.o.
> "^vot,.*":
> description: Vision Optical Technology Co., Ltd.
> + "^vxt,.*"
> + description: VXT Ltd
> "^wd,.*":
> description: Western Digital Corp.
> "^wetek,.*":
> --
> 2.20.1
In doing a back merge of Linus' tree into the drm-misc tree, you seem
to have missed the above merge fixup and so lost some of the changes
from the above commits.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-21 0:51 linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
` (4 preceding siblings ...)
2019-05-23 0:27 ` linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
@ 2019-05-23 8:10 ` Maxime Ripard
2019-05-23 9:34 ` Stephen Rothwell
2019-05-23 11:53 ` Maxime Ripard
6 siblings, 1 reply; 18+ messages in thread
From: Maxime Ripard @ 2019-05-23 8:10 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Daniel Vetter, Intel Graphics, DRI, Linux Kernel Mailing List,
Jyri Sarha, Marco Felsch, Linux Next Mailing List,
Thierry Reding
[-- Attachment #1: Type: text/plain, Size: 2717 bytes --]
Hi Stephen,
On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
>
> Documentation/devicetree/bindings/vendor-prefixes.txt
>
> between commit:
>
> 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
>
> from Linus' tree and commits:
>
> b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
>
> from the drm-misc tree.
>
> I fixed it up (I deleted the file and added the patch below) and can
> carry the fix as necessary. This is now fixed as far as linux-next is
> concerned, but any non trivial conflicts should be mentioned to your
> upstream maintainer when your tree is submitted for merging. You may
> also want to consider cooperating with the maintainer of the conflicting
> tree to minimise any particularly complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 21 May 2019 10:48:36 +1000
> Subject: [PATCH] dt-bindings: fix up for vendor prefixes file conversion
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 83ca4816a78b..749e3c3843d0 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -287,6 +287,8 @@ patternProperties:
> description: Everest Semiconductor Co. Ltd.
> "^everspin,.*":
> description: Everspin Technologies, Inc.
> + "^evervision,.*":
> + description: Evervision Electronics Co. Ltd.
> "^exar,.*":
> description: Exar Corporation
> "^excito,.*":
> @@ -851,6 +853,8 @@ patternProperties:
> description: Shenzhen Techstar Electronics Co., Ltd.
> "^terasic,.*":
> description: Terasic Inc.
> + "^tfc,.*":
> + description: Three Five Corp
> "^thine,.*":
> description: THine Electronics, Inc.
> "^ti,.*":
> @@ -925,6 +929,8 @@ patternProperties:
> description: Voipac Technologies s.r.o.
> "^vot,.*":
> description: Vision Optical Technology Co., Ltd.
> + "^vxt,.*"
> + description: VXT Ltd
I'm not sure whether or not you can change it, but this breaks the
users of that file.
What you want is:
- "^vxt,.*"
+ "^vxt,.*:"
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-23 8:10 ` Maxime Ripard
@ 2019-05-23 9:34 ` Stephen Rothwell
0 siblings, 0 replies; 18+ messages in thread
From: Stephen Rothwell @ 2019-05-23 9:34 UTC (permalink / raw)
To: Maxime Ripard
Cc: Daniel Vetter, Intel Graphics, DRI, Linux Kernel Mailing List,
Jyri Sarha, Marco Felsch, Linux Next Mailing List,
Thierry Reding, Sean Paul
[-- Attachment #1: Type: text/plain, Size: 3101 bytes --]
Hi Maxime,
On Thu, 23 May 2019 10:10:22 +0200 Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> Hi Stephen,
>
> On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the drm-misc tree got a conflict in:
> >
> > Documentation/devicetree/bindings/vendor-prefixes.txt
> >
> > between commit:
> >
> > 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
> >
> > from Linus' tree and commits:
> >
> > b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> > b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> > fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
> >
> > from the drm-misc tree.
> >
> > I fixed it up (I deleted the file and added the patch below) and can
> > carry the fix as necessary. This is now fixed as far as linux-next is
> > concerned, but any non trivial conflicts should be mentioned to your
> > upstream maintainer when your tree is submitted for merging. You may
> > also want to consider cooperating with the maintainer of the conflicting
> > tree to minimise any particularly complex conflicts.
> >
> > --
> > Cheers,
> > Stephen Rothwell
> >
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Tue, 21 May 2019 10:48:36 +1000
> > Subject: [PATCH] dt-bindings: fix up for vendor prefixes file conversion
> >
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > ---
> > Documentation/devicetree/bindings/vendor-prefixes.yaml | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > index 83ca4816a78b..749e3c3843d0 100644
> > --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > @@ -287,6 +287,8 @@ patternProperties:
> > description: Everest Semiconductor Co. Ltd.
> > "^everspin,.*":
> > description: Everspin Technologies, Inc.
> > + "^evervision,.*":
> > + description: Evervision Electronics Co. Ltd.
> > "^exar,.*":
> > description: Exar Corporation
> > "^excito,.*":
> > @@ -851,6 +853,8 @@ patternProperties:
> > description: Shenzhen Techstar Electronics Co., Ltd.
> > "^terasic,.*":
> > description: Terasic Inc.
> > + "^tfc,.*":
> > + description: Three Five Corp
> > "^thine,.*":
> > description: THine Electronics, Inc.
> > "^ti,.*":
> > @@ -925,6 +929,8 @@ patternProperties:
> > description: Voipac Technologies s.r.o.
> > "^vot,.*":
> > description: Vision Optical Technology Co., Ltd.
> > + "^vxt,.*"
> > + description: VXT Ltd
>
> I'm not sure whether or not you can change it, but this breaks the
> users of that file.
>
> What you want is:
>
> - "^vxt,.*"
> + "^vxt,.*:"
I have fixed my version (but I put the ':' after the '"' like the
others).
Thanks for letting me know.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-21 0:51 linux-next: manual merge of the drm-misc tree with Linus' tree Stephen Rothwell
@ 2019-05-23 11:53 ` Maxime Ripard
2019-05-21 15:08 ` ✗ Fi.CI.CHECKPATCH: warning for linux-next: manual merge of the drm-misc tree with Linus' tree (rev2) Patchwork
` (5 subsequent siblings)
6 siblings, 0 replies; 18+ messages in thread
From: Maxime Ripard @ 2019-05-23 11:53 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Daniel Vetter, Intel Graphics, DRI, Linux Kernel Mailing List,
Jyri Sarha, Marco Felsch, Linux Next Mailing List,
Thierry Reding
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
>
> Documentation/devicetree/bindings/vendor-prefixes.txt
>
> between commit:
>
> 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
>
> from Linus' tree and commits:
>
> b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
>
> from the drm-misc tree.
>
> I fixed it up (I deleted the file and added the patch below) and can
> carry the fix as necessary. This is now fixed as far as linux-next is
> concerned, but any non trivial conflicts should be mentioned to your
> upstream maintainer when your tree is submitted for merging. You may
> also want to consider cooperating with the maintainer of the conflicting
> tree to minimise any particularly complex conflicts.
I just took your patch and pushed a temp branch there:
https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next&id=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90
Rob, Stephen, are you ok with the change? If so, I'll push it.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
@ 2019-05-23 11:53 ` Maxime Ripard
0 siblings, 0 replies; 18+ messages in thread
From: Maxime Ripard @ 2019-05-23 11:53 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Daniel Vetter, Intel Graphics, Linux Kernel Mailing List,
Jyri Sarha, Marco Felsch, Linux Next Mailing List, DRI,
Thierry Reding
[-- Attachment #1.1: Type: text/plain, Size: 1363 bytes --]
On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
>
> Documentation/devicetree/bindings/vendor-prefixes.txt
>
> between commit:
>
> 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
>
> from Linus' tree and commits:
>
> b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
>
> from the drm-misc tree.
>
> I fixed it up (I deleted the file and added the patch below) and can
> carry the fix as necessary. This is now fixed as far as linux-next is
> concerned, but any non trivial conflicts should be mentioned to your
> upstream maintainer when your tree is submitted for merging. You may
> also want to consider cooperating with the maintainer of the conflicting
> tree to minimise any particularly complex conflicts.
I just took your patch and pushed a temp branch there:
https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next&id=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90
Rob, Stephen, are you ok with the change? If so, I'll push it.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-23 11:53 ` Maxime Ripard
(?)
@ 2019-05-23 13:04 ` Stephen Rothwell
2019-05-23 13:11 ` Daniel Vetter
-1 siblings, 1 reply; 18+ messages in thread
From: Stephen Rothwell @ 2019-05-23 13:04 UTC (permalink / raw)
To: Maxime Ripard
Cc: Daniel Vetter, Intel Graphics, DRI, Linux Kernel Mailing List,
Jyri Sarha, Marco Felsch, Linux Next Mailing List,
Thierry Reding, Sean Paul
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
Hi Maxime,
On Thu, 23 May 2019 13:53:55 +0200 Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> >
> > Today's linux-next merge of the drm-misc tree got a conflict in:
> >
> > Documentation/devicetree/bindings/vendor-prefixes.txt
> >
> > between commit:
> >
> > 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
> >
> > from Linus' tree and commits:
> >
> > b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> > b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> > fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
> >
> > from the drm-misc tree.
>
> I just took your patch and pushed a temp branch there:
> https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next&id=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90
>
> Rob, Stephen, are you ok with the change? If so, I'll push it.
All that needs to be done is for my patch (slightly corrected) needs to
be applied to the drm-misc tree. That tree already has the back merge
of Linus' tree and the txt file has been removed (my patch should have
been applied as part of the merge resolution but doing it later is fine).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-23 13:04 ` Stephen Rothwell
@ 2019-05-23 13:11 ` Daniel Vetter
2019-05-23 14:16 ` Stephen Rothwell
0 siblings, 1 reply; 18+ messages in thread
From: Daniel Vetter @ 2019-05-23 13:11 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Maxime Ripard, Intel Graphics, DRI, Linux Kernel Mailing List,
Jyri Sarha, Marco Felsch, Linux Next Mailing List,
Thierry Reding, Sean Paul
On Thu, May 23, 2019 at 3:04 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Maxime,
>
> On Thu, 23 May 2019 13:53:55 +0200 Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> >
> > On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> > >
> > > Today's linux-next merge of the drm-misc tree got a conflict in:
> > >
> > > Documentation/devicetree/bindings/vendor-prefixes.txt
> > >
> > > between commit:
> > >
> > > 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
> > >
> > > from Linus' tree and commits:
> > >
> > > b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> > > b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> > > fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
> > >
> > > from the drm-misc tree.
> >
> > I just took your patch and pushed a temp branch there:
> > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next&id=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90
> >
> > Rob, Stephen, are you ok with the change? If so, I'll push it.
>
> All that needs to be done is for my patch (slightly corrected) needs to
> be applied to the drm-misc tree. That tree already has the back merge
> of Linus' tree and the txt file has been removed (my patch should have
> been applied as part of the merge resolution but doing it later is fine).
That commit is on top of drm-misc, and somehow the .txt version has
been resurrect in drm-misc-next (so needs to be re-deleted too).
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-23 13:11 ` Daniel Vetter
@ 2019-05-23 14:16 ` Stephen Rothwell
0 siblings, 0 replies; 18+ messages in thread
From: Stephen Rothwell @ 2019-05-23 14:16 UTC (permalink / raw)
To: Daniel Vetter
Cc: Maxime Ripard, Intel Graphics, DRI, Linux Kernel Mailing List,
Jyri Sarha, Marco Felsch, Linux Next Mailing List,
Thierry Reding, Sean Paul
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
Hi Daniel,
On Thu, 23 May 2019 15:11:15 +0200 Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> That commit is on top of drm-misc, and somehow the .txt version has
> been resurrect in drm-misc-next (so needs to be re-deleted too).
My mistake, the conflict went away (due to the back merge) so my
scripts assumed the file no longer needed deleting. I didn't actually
check to see if it was still there.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
@ 2019-05-23 14:16 ` Stephen Rothwell
0 siblings, 0 replies; 18+ messages in thread
From: Stephen Rothwell @ 2019-05-23 14:16 UTC (permalink / raw)
To: Daniel Vetter
Cc: Maxime Ripard, Intel Graphics, Linux Kernel Mailing List,
Jyri Sarha, Marco Felsch, Linux Next Mailing List, Sean Paul,
DRI, Thierry Reding
[-- Attachment #1.1: Type: text/plain, Size: 449 bytes --]
Hi Daniel,
On Thu, 23 May 2019 15:11:15 +0200 Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> That commit is on top of drm-misc, and somehow the .txt version has
> been resurrect in drm-misc-next (so needs to be re-deleted too).
My mistake, the conflict went away (due to the back merge) so my
scripts assumed the file no longer needed deleting. I didn't actually
check to see if it was still there.
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-23 11:53 ` Maxime Ripard
@ 2019-05-23 16:10 ` Rob Herring
-1 siblings, 0 replies; 18+ messages in thread
From: Rob Herring @ 2019-05-23 16:10 UTC (permalink / raw)
To: Maxime Ripard
Cc: Stephen Rothwell, Daniel Vetter, Intel Graphics,
Linux Kernel Mailing List, Jyri Sarha, Marco Felsch,
Linux Next Mailing List, DRI, Thierry Reding
On Thu, May 23, 2019 at 6:54 AM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the drm-misc tree got a conflict in:
> >
> > Documentation/devicetree/bindings/vendor-prefixes.txt
> >
> > between commit:
> >
> > 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
> >
> > from Linus' tree and commits:
> >
> > b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> > b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> > fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
> >
> > from the drm-misc tree.
> >
> > I fixed it up (I deleted the file and added the patch below) and can
> > carry the fix as necessary. This is now fixed as far as linux-next is
> > concerned, but any non trivial conflicts should be mentioned to your
> > upstream maintainer when your tree is submitted for merging. You may
> > also want to consider cooperating with the maintainer of the conflicting
> > tree to minimise any particularly complex conflicts.
>
> I just took your patch and pushed a temp branch there:
> https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next&id=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90
>
> Rob, Stephen, are you ok with the change? If so, I'll push it.
The 'tfc' line is missing a ':' on the end. Does the file pass
dt_binding_check like that?
Rob
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
@ 2019-05-23 16:10 ` Rob Herring
0 siblings, 0 replies; 18+ messages in thread
From: Rob Herring @ 2019-05-23 16:10 UTC (permalink / raw)
To: Maxime Ripard
Cc: Stephen Rothwell, Daniel Vetter, Intel Graphics, Marco Felsch,
Jyri Sarha, Linux Kernel Mailing List, Linux Next Mailing List,
DRI, Thierry Reding
On Thu, May 23, 2019 at 6:54 AM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the drm-misc tree got a conflict in:
> >
> > Documentation/devicetree/bindings/vendor-prefixes.txt
> >
> > between commit:
> >
> > 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
> >
> > from Linus' tree and commits:
> >
> > b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> > b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> > fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
> >
> > from the drm-misc tree.
> >
> > I fixed it up (I deleted the file and added the patch below) and can
> > carry the fix as necessary. This is now fixed as far as linux-next is
> > concerned, but any non trivial conflicts should be mentioned to your
> > upstream maintainer when your tree is submitted for merging. You may
> > also want to consider cooperating with the maintainer of the conflicting
> > tree to minimise any particularly complex conflicts.
>
> I just took your patch and pushed a temp branch there:
> https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next&id=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90
>
> Rob, Stephen, are you ok with the change? If so, I'll push it.
The 'tfc' line is missing a ':' on the end. Does the file pass
dt_binding_check like that?
Rob
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
2019-05-23 16:10 ` Rob Herring
@ 2019-05-24 7:12 ` Maxime Ripard
-1 siblings, 0 replies; 18+ messages in thread
From: Maxime Ripard @ 2019-05-24 7:12 UTC (permalink / raw)
To: Rob Herring
Cc: Stephen Rothwell, Daniel Vetter, Intel Graphics,
Linux Kernel Mailing List, Jyri Sarha, Marco Felsch,
Linux Next Mailing List, DRI, Thierry Reding
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
On Thu, May 23, 2019 at 11:10:39AM -0500, Rob Herring wrote:
> On Thu, May 23, 2019 at 6:54 AM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> >
> > On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Today's linux-next merge of the drm-misc tree got a conflict in:
> > >
> > > Documentation/devicetree/bindings/vendor-prefixes.txt
> > >
> > > between commit:
> > >
> > > 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
> > >
> > > from Linus' tree and commits:
> > >
> > > b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> > > b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> > > fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
> > >
> > > from the drm-misc tree.
> > >
> > > I fixed it up (I deleted the file and added the patch below) and can
> > > carry the fix as necessary. This is now fixed as far as linux-next is
> > > concerned, but any non trivial conflicts should be mentioned to your
> > > upstream maintainer when your tree is submitted for merging. You may
> > > also want to consider cooperating with the maintainer of the conflicting
> > > tree to minimise any particularly complex conflicts.
> >
> > I just took your patch and pushed a temp branch there:
> > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next&id=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90
> >
> > Rob, Stephen, are you ok with the change? If so, I'll push it.
>
> The 'tfc' line is missing a ':' on the end.
That's on me, sorry.
> Does the file pass dt_binding_check like that?
No, it didn't but I overlooked it somehow. I've pushed that patch with
the extra semi-column.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: linux-next: manual merge of the drm-misc tree with Linus' tree
@ 2019-05-24 7:12 ` Maxime Ripard
0 siblings, 0 replies; 18+ messages in thread
From: Maxime Ripard @ 2019-05-24 7:12 UTC (permalink / raw)
To: Rob Herring
Cc: Stephen Rothwell, Daniel Vetter, Intel Graphics, Marco Felsch,
Jyri Sarha, Linux Kernel Mailing List, Linux Next Mailing List,
DRI, Thierry Reding
[-- Attachment #1.1: Type: text/plain, Size: 1844 bytes --]
On Thu, May 23, 2019 at 11:10:39AM -0500, Rob Herring wrote:
> On Thu, May 23, 2019 at 6:54 AM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> >
> > On Tue, May 21, 2019 at 10:51:51AM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Today's linux-next merge of the drm-misc tree got a conflict in:
> > >
> > > Documentation/devicetree/bindings/vendor-prefixes.txt
> > >
> > > between commit:
> > >
> > > 8122de54602e ("dt-bindings: Convert vendor prefixes to json-schema")
> > >
> > > from Linus' tree and commits:
> > >
> > > b4a2c0055a4f ("dt-bindings: Add vendor prefix for VXT Ltd")
> > > b1b0d36bdb15 ("dt-bindings: drm/panel: simple: Add binding for TFC S9700RTWV43TR-01B")
> > > fbd8b69ab616 ("dt-bindings: Add vendor prefix for Evervision Electronics")
> > >
> > > from the drm-misc tree.
> > >
> > > I fixed it up (I deleted the file and added the patch below) and can
> > > carry the fix as necessary. This is now fixed as far as linux-next is
> > > concerned, but any non trivial conflicts should be mentioned to your
> > > upstream maintainer when your tree is submitted for merging. You may
> > > also want to consider cooperating with the maintainer of the conflicting
> > > tree to minimise any particularly complex conflicts.
> >
> > I just took your patch and pushed a temp branch there:
> > https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next&id=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90
> >
> > Rob, Stephen, are you ok with the change? If so, I'll push it.
>
> The 'tfc' line is missing a ':' on the end.
That's on me, sorry.
> Does the file pass dt_binding_check like that?
No, it didn't but I overlooked it somehow. I've pushed that patch with
the extra semi-column.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread