* [Intel-gfx] [PATCH] dma-buf.rst: repair length of title underline
@ 2020-08-09 6:17 Lukas Bulwahn
2020-08-09 6:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Lukas Bulwahn @ 2020-08-09 6:17 UTC (permalink / raw)
To: Daniel Vetter
Cc: linux-doc, linux-rdma, intel-gfx, Jonathan Corbet, linux-kernel,
amd-gfx, Christian König, linaro-mm-sig, dri-devel,
Lukas Bulwahn, Sumit Semwal, linux-media
With commit 72b6ede73623 ("dma-buf.rst: Document why indefinite fences are
a bad idea"), document generation warns:
Documentation/driver-api/dma-buf.rst:182: \
WARNING: Title underline too short.
Repair length of title underline to remove warning.
Fixes: 72b6ede73623 ("dma-buf.rst: Document why indefinite fences are a bad idea")
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
Daniel, please pick this minor non-urgent fix to your new documentation.
Documentation/driver-api/dma-buf.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/driver-api/dma-buf.rst b/Documentation/driver-api/dma-buf.rst
index 100bfd227265..13ea0cc0a3fa 100644
--- a/Documentation/driver-api/dma-buf.rst
+++ b/Documentation/driver-api/dma-buf.rst
@@ -179,7 +179,7 @@ DMA Fence uABI/Sync File
:internal:
Indefinite DMA Fences
-~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~
At various times &dma_fence with an indefinite time until dma_fence_wait()
finishes have been proposed. Examples include:
--
2.17.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for dma-buf.rst: repair length of title underline
2020-08-09 6:17 [Intel-gfx] [PATCH] dma-buf.rst: repair length of title underline Lukas Bulwahn
@ 2020-08-09 6:48 ` Patchwork
2020-08-09 8:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-08-10 11:25 ` [Intel-gfx] [PATCH] " Christian König
2 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2020-08-09 6:48 UTC (permalink / raw)
To: Lukas Bulwahn; +Cc: intel-gfx
[-- Attachment #1.1: Type: text/plain, Size: 4222 bytes --]
== Series Details ==
Series: dma-buf.rst: repair length of title underline
URL : https://patchwork.freedesktop.org/series/80428/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8861 -> Patchwork_18328
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/index.html
Known issues
------------
Here are the changes found in Patchwork_18328 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_flip@basic-flip-vs-wf_vblank@c-hdmi-a2:
- fi-skl-guc: [PASS][1] -> [DMESG-WARN][2] ([i915#2203])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/fi-skl-guc/igt@kms_flip@basic-flip-vs-wf_vblank@c-hdmi-a2.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/fi-skl-guc/igt@kms_flip@basic-flip-vs-wf_vblank@c-hdmi-a2.html
#### Possible fixes ####
* igt@i915_module_load@reload:
- fi-byt-j1900: [DMESG-WARN][3] ([i915#1982]) -> [PASS][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/fi-byt-j1900/igt@i915_module_load@reload.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/fi-byt-j1900/igt@i915_module_load@reload.html
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-kefka: [DMESG-WARN][5] ([i915#1982]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/fi-bsw-kefka/igt@i915_pm_rpm@basic-pci-d3-state.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/fi-bsw-kefka/igt@i915_pm_rpm@basic-pci-d3-state.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-icl-u2: [DMESG-WARN][7] ([i915#1982]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
#### Warnings ####
* igt@kms_force_connector_basic@force-connector-state:
- fi-kbl-x1275: [DMESG-WARN][9] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][10] ([i915#62] / [i915#92]) +2 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/fi-kbl-x1275/igt@kms_force_connector_basic@force-connector-state.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/fi-kbl-x1275/igt@kms_force_connector_basic@force-connector-state.html
* igt@kms_force_connector_basic@force-edid:
- fi-kbl-x1275: [DMESG-WARN][11] ([i915#62] / [i915#92]) -> [DMESG-WARN][12] ([i915#62] / [i915#92] / [i915#95]) +3 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/fi-kbl-x1275/igt@kms_force_connector_basic@force-edid.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/fi-kbl-x1275/igt@kms_force_connector_basic@force-edid.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2203]: https://gitlab.freedesktop.org/drm/intel/issues/2203
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (43 -> 37)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8861 -> Patchwork_18328
CI-20190529: 20190529
CI_DRM_8861: bf06cb001cd5b243d35b115c43f47fa11bd27d3b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5765: 9f0977284d54ed37496260988dfcd6d2ad72dd1e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18328: 9e7af991aca443b5baedcae916a70aaed6c0c48d @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
9e7af991aca4 dma-buf.rst: repair length of title underline
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/index.html
[-- Attachment #1.2: Type: text/html, Size: 5555 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for dma-buf.rst: repair length of title underline
2020-08-09 6:17 [Intel-gfx] [PATCH] dma-buf.rst: repair length of title underline Lukas Bulwahn
2020-08-09 6:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
@ 2020-08-09 8:33 ` Patchwork
2020-08-10 11:25 ` [Intel-gfx] [PATCH] " Christian König
2 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2020-08-09 8:33 UTC (permalink / raw)
To: Lukas Bulwahn; +Cc: intel-gfx
[-- Attachment #1.1: Type: text/plain, Size: 12493 bytes --]
== Series Details ==
Series: dma-buf.rst: repair length of title underline
URL : https://patchwork.freedesktop.org/series/80428/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8861_full -> Patchwork_18328_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_18328_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_18328_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_18328_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_softpin@noreloc-s3:
- shard-skl: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-skl1/igt@gem_softpin@noreloc-s3.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-skl9/igt@gem_softpin@noreloc-s3.html
Known issues
------------
Here are the changes found in Patchwork_18328_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_balancer@nop:
- shard-iclb: [PASS][3] -> [INCOMPLETE][4] ([i915#2268])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-iclb1/igt@gem_exec_balancer@nop.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-iclb4/igt@gem_exec_balancer@nop.html
* igt@gem_exec_whisper@basic-contexts-forked:
- shard-glk: [PASS][5] -> [DMESG-WARN][6] ([i915#118] / [i915#95])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-glk9/igt@gem_exec_whisper@basic-contexts-forked.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-glk8/igt@gem_exec_whisper@basic-contexts-forked.html
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][7] -> [SKIP][8] ([i915#2190])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-tglb1/igt@gem_huc_copy@huc-copy.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-tglb6/igt@gem_huc_copy@huc-copy.html
* igt@i915_selftest@mock@requests:
- shard-apl: [PASS][9] -> [INCOMPLETE][10] ([i915#1635])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-apl7/igt@i915_selftest@mock@requests.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-apl2/igt@i915_selftest@mock@requests.html
* igt@kms_big_fb@x-tiled-64bpp-rotate-180:
- shard-glk: [PASS][11] -> [DMESG-FAIL][12] ([i915#118] / [i915#95])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-glk5/igt@kms_big_fb@x-tiled-64bpp-rotate-180.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-glk8/igt@kms_big_fb@x-tiled-64bpp-rotate-180.html
* igt@kms_color@pipe-c-ctm-0-5:
- shard-skl: [PASS][13] -> [DMESG-WARN][14] ([i915#1982]) +6 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-skl1/igt@kms_color@pipe-c-ctm-0-5.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-skl3/igt@kms_color@pipe-c-ctm-0-5.html
* igt@kms_draw_crc@draw-method-xrgb2101010-mmap-cpu-ytiled:
- shard-glk: [PASS][15] -> [DMESG-WARN][16] ([i915#1982])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-glk3/igt@kms_draw_crc@draw-method-xrgb2101010-mmap-cpu-ytiled.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-glk3/igt@kms_draw_crc@draw-method-xrgb2101010-mmap-cpu-ytiled.html
* igt@kms_flip@2x-flip-vs-fences-interruptible@ab-vga1-hdmi-a1:
- shard-hsw: [PASS][17] -> [DMESG-WARN][18] ([i915#1982]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-hsw1/igt@kms_flip@2x-flip-vs-fences-interruptible@ab-vga1-hdmi-a1.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-hsw1/igt@kms_flip@2x-flip-vs-fences-interruptible@ab-vga1-hdmi-a1.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [PASS][19] -> [DMESG-WARN][20] ([i915#180]) +13 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-suspend.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-kbl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][21] -> [FAIL][22] ([i915#1188])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-skl3/igt@kms_hdr@bpc-switch-dpms.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-skl4/igt@kms_hdr@bpc-switch-dpms.html
#### Possible fixes ####
* igt@gem_ctx_isolation@preservation-s3@vcs0:
- shard-skl: [INCOMPLETE][23] ([i915#198]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-skl8/igt@gem_ctx_isolation@preservation-s3@vcs0.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-skl8/igt@gem_ctx_isolation@preservation-s3@vcs0.html
* igt@gem_exec_gttfill@engines@rcs0:
- shard-glk: [DMESG-WARN][25] ([i915#118] / [i915#95]) -> [PASS][26] +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-glk4/igt@gem_exec_gttfill@engines@rcs0.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-glk3/igt@gem_exec_gttfill@engines@rcs0.html
* igt@kms_big_fb@y-tiled-64bpp-rotate-0:
- shard-glk: [DMESG-FAIL][27] ([i915#118] / [i915#95]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-glk8/igt@kms_big_fb@y-tiled-64bpp-rotate-0.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-glk5/igt@kms_big_fb@y-tiled-64bpp-rotate-0.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-skl: [INCOMPLETE][29] ([i915#300]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-skl5/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-skl6/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_cursor_edge_walk@pipe-c-128x128-bottom-edge:
- shard-glk: [DMESG-WARN][31] ([i915#1982]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-glk4/igt@kms_cursor_edge_walk@pipe-c-128x128-bottom-edge.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-glk6/igt@kms_cursor_edge_walk@pipe-c-128x128-bottom-edge.html
* igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic:
- shard-snb: [SKIP][33] ([fdo#109271]) -> [PASS][34] +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-snb2/igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-snb2/igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][35] ([i915#79]) -> [PASS][36] +2 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-glk3/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-glk2/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html
* igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-cpu:
- shard-kbl: [DMESG-WARN][37] ([i915#1982]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-cpu.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite:
- shard-tglb: [DMESG-WARN][39] ([i915#1982]) -> [PASS][40] +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-tglb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-tglb3/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite.html
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [DMESG-WARN][41] ([i915#180]) -> [PASS][42] +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-kbl1/igt@kms_hdr@bpc-switch-suspend.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-kbl7/igt@kms_hdr@bpc-switch-suspend.html
* igt@kms_plane@plane-position-covered-pipe-b-planes:
- shard-skl: [DMESG-WARN][43] ([i915#1982]) -> [PASS][44] +12 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-skl6/igt@kms_plane@plane-position-covered-pipe-b-planes.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-skl3/igt@kms_plane@plane-position-covered-pipe-b-planes.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][45] ([fdo#109441]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-iclb8/igt@kms_psr@psr2_primary_mmap_cpu.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_setmode@basic:
- shard-hsw: [FAIL][47] ([i915#31]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-hsw4/igt@kms_setmode@basic.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-hsw6/igt@kms_setmode@basic.html
#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-kbl: [TIMEOUT][49] ([i915#1319]) -> [TIMEOUT][50] ([i915#1319] / [i915#1958])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-kbl7/igt@kms_content_protection@atomic.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-kbl6/igt@kms_content_protection@atomic.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [DMESG-WARN][51] ([i915#180]) -> [INCOMPLETE][52] ([i915#155])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8861/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18328/shard-kbl2/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2268]: https://gitlab.freedesktop.org/drm/intel/issues/2268
[i915#300]: https://gitlab.freedesktop.org/drm/intel/issues/300
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8861 -> Patchwork_18328
CI-20190529: 20190529
CI_DRM_8861: bf06cb001cd5b243d35b115c43f47fa11bd27d3b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5765: 9f0977284d54ed37496260988dfcd6d2ad72dd1e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18328: 9e7af991aca443b5baedcae916a70aaed6c0c48d @ 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_18328/index.html
[-- Attachment #1.2: Type: text/html, Size: 14741 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Intel-gfx] [PATCH] dma-buf.rst: repair length of title underline
2020-08-09 6:17 [Intel-gfx] [PATCH] dma-buf.rst: repair length of title underline Lukas Bulwahn
2020-08-09 6:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-08-09 8:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
@ 2020-08-10 11:25 ` Christian König
2020-08-10 13:06 ` Daniel Vetter
2 siblings, 1 reply; 5+ messages in thread
From: Christian König @ 2020-08-10 11:25 UTC (permalink / raw)
To: Lukas Bulwahn, Daniel Vetter
Cc: Jonathan Corbet, linux-rdma, intel-gfx, linux-doc, linux-kernel,
amd-gfx, Sumit Semwal, linaro-mm-sig, dri-devel,
Christian König, linux-media
Am 09.08.20 um 08:17 schrieb Lukas Bulwahn:
> With commit 72b6ede73623 ("dma-buf.rst: Document why indefinite fences are
> a bad idea"), document generation warns:
>
> Documentation/driver-api/dma-buf.rst:182: \
> WARNING: Title underline too short.
>
> Repair length of title underline to remove warning.
>
> Fixes: 72b6ede73623 ("dma-buf.rst: Document why indefinite fences are a bad idea")
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Acked-by: Christian König <christian.koenig@amd.com>
Should I pick it up into drm-misc-next?
> ---
> Daniel, please pick this minor non-urgent fix to your new documentation.
>
> Documentation/driver-api/dma-buf.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/driver-api/dma-buf.rst b/Documentation/driver-api/dma-buf.rst
> index 100bfd227265..13ea0cc0a3fa 100644
> --- a/Documentation/driver-api/dma-buf.rst
> +++ b/Documentation/driver-api/dma-buf.rst
> @@ -179,7 +179,7 @@ DMA Fence uABI/Sync File
> :internal:
>
> Indefinite DMA Fences
> -~~~~~~~~~~~~~~~~~~~~
> +~~~~~~~~~~~~~~~~~~~~~
>
> At various times &dma_fence with an indefinite time until dma_fence_wait()
> finishes have been proposed. Examples include:
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Intel-gfx] [PATCH] dma-buf.rst: repair length of title underline
2020-08-10 11:25 ` [Intel-gfx] [PATCH] " Christian König
@ 2020-08-10 13:06 ` Daniel Vetter
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Vetter @ 2020-08-10 13:06 UTC (permalink / raw)
To: christian.koenig
Cc: linux-doc, linux-rdma, Daniel Vetter, intel-gfx, Jonathan Corbet,
linux-kernel, amd-gfx, linaro-mm-sig, dri-devel, Lukas Bulwahn,
Sumit Semwal, linux-media
On Mon, Aug 10, 2020 at 01:25:40PM +0200, Christian König wrote:
> Am 09.08.20 um 08:17 schrieb Lukas Bulwahn:
> > With commit 72b6ede73623 ("dma-buf.rst: Document why indefinite fences are
> > a bad idea"), document generation warns:
> >
> > Documentation/driver-api/dma-buf.rst:182: \
> > WARNING: Title underline too short.
> >
> > Repair length of title underline to remove warning.
> >
> > Fixes: 72b6ede73623 ("dma-buf.rst: Document why indefinite fences are a bad idea")
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>
> Acked-by: Christian König <christian.koenig@amd.com>
>
> Should I pick it up into drm-misc-next?
Yes please. For the future if you need to check if someone has commit
rights and can push themselves:
https://people.freedesktop.org/~seanpaul/whomisc.html
Yeah with gitlab this would all be a bit more reasonable, but we get by
meanwhile :-)
Cheers, Daniel
>
> > ---
> > Daniel, please pick this minor non-urgent fix to your new documentation.
> >
> > Documentation/driver-api/dma-buf.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/driver-api/dma-buf.rst b/Documentation/driver-api/dma-buf.rst
> > index 100bfd227265..13ea0cc0a3fa 100644
> > --- a/Documentation/driver-api/dma-buf.rst
> > +++ b/Documentation/driver-api/dma-buf.rst
> > @@ -179,7 +179,7 @@ DMA Fence uABI/Sync File
> > :internal:
> > Indefinite DMA Fences
> > -~~~~~~~~~~~~~~~~~~~~
> > +~~~~~~~~~~~~~~~~~~~~~
> > At various times &dma_fence with an indefinite time until dma_fence_wait()
> > finishes have been proposed. Examples include:
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-08-10 13:59 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-08-09 6:17 [Intel-gfx] [PATCH] dma-buf.rst: repair length of title underline Lukas Bulwahn
2020-08-09 6:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-08-09 8:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-08-10 11:25 ` [Intel-gfx] [PATCH] " Christian König
2020-08-10 13:06 ` Daniel Vetter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox