* linux-next: build warnings after merge of the drm-misc-fixes tree
@ 2025-08-18 2:38 Stephen Rothwell
2025-08-18 5:56 ` Bagas Sanjaya
0 siblings, 1 reply; 5+ messages in thread
From: Stephen Rothwell @ 2025-08-18 2:38 UTC (permalink / raw)
To: Simona Vetter, Rob Clark, Sean Paul
Cc: Bagas Sanjaya, Rob Clark, Danilo Krummrich, Javier Garcia,
Intel Graphics, DRI, Linux Kernel Mailing List,
Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]
Hi all,
After merging the drm-misc-fixes tree, today's linux-next build (htmldocs)
produced these warnings:
Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2446: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2448: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2452: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2453: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2457: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2458: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2459: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2460: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
Introduced by commit
6cc44e9618f0 ("drm: Add directive to format code in comment")
interacting with commit
bb324f85f722 ("drm/gpuvm: Wrap drm_gpuvm_sm_map_exec_lock() expected usage in literal code block")
from the drm-msm-fixes tree. Both get applied.
The drm-misc-fixes commit is unneeded.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: linux-next: build warnings after merge of the drm-misc-fixes tree
2025-08-18 2:38 linux-next: build warnings after merge of the drm-misc-fixes tree Stephen Rothwell
@ 2025-08-18 5:56 ` Bagas Sanjaya
2025-08-18 8:24 ` Danilo Krummrich
2025-08-20 18:35 ` Bala-Vignesh-Reddy
0 siblings, 2 replies; 5+ messages in thread
From: Bagas Sanjaya @ 2025-08-18 5:56 UTC (permalink / raw)
To: Stephen Rothwell, Simona Vetter, Rob Clark, Sean Paul
Cc: Rob Clark, Danilo Krummrich, Javier Garcia, Intel Graphics, DRI,
Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
On Mon, Aug 18, 2025 at 12:38:53PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drm-misc-fixes tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2446: ERROR: Unexpected indentation. [docutils]
> Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2448: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
> Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2452: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
> Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2453: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
> Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2457: ERROR: Unexpected indentation. [docutils]
> Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2458: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
> Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2459: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
> Documentation/gpu/drm-mm:506: drivers/gpu/drm/drm_gpuvm.c:2460: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
>
> Introduced by commit
>
> 6cc44e9618f0 ("drm: Add directive to format code in comment")
>
> interacting with commit
>
> bb324f85f722 ("drm/gpuvm: Wrap drm_gpuvm_sm_map_exec_lock() expected usage in literal code block")
Duh! drm_gpuvm.c gets tangled...
Danilo, can you please drop my commit (and kept Javier's one)?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: linux-next: build warnings after merge of the drm-misc-fixes tree
2025-08-18 5:56 ` Bagas Sanjaya
@ 2025-08-18 8:24 ` Danilo Krummrich
2025-08-20 18:35 ` Bala-Vignesh-Reddy
1 sibling, 0 replies; 5+ messages in thread
From: Danilo Krummrich @ 2025-08-18 8:24 UTC (permalink / raw)
To: Bagas Sanjaya, Rob Clark
Cc: Stephen Rothwell, Simona Vetter, Rob Clark, Sean Paul,
Javier Garcia, Intel Graphics, DRI, Linux Kernel Mailing List,
Linux Next Mailing List
On 8/18/25 7:56 AM, Bagas Sanjaya wrote:
> Danilo, can you please drop my commit (and kept Javier's one)?
I think yours is in drm-msm-fixes, which I don't maintain.
@Rob: Can you drop it please?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: linux-next: build warnings after merge of the drm-misc-fixes tree
2025-08-18 5:56 ` Bagas Sanjaya
2025-08-18 8:24 ` Danilo Krummrich
@ 2025-08-20 18:35 ` Bala-Vignesh-Reddy
2025-08-21 3:50 ` Bagas Sanjaya
1 sibling, 1 reply; 5+ messages in thread
From: Bala-Vignesh-Reddy @ 2025-08-20 18:35 UTC (permalink / raw)
To: bagasdotme
Cc: dakr, dri-devel, intel-gfx, linux-kernel, linux-next, rampxxxx,
robdclark, robin.clark, seanpaul, sfr, simona.vetter
Hi all,
Those htmldocs warnings come from missing Sphinx markup in
`drm_gpuvm_sm_map_exec_lock()`.
This is already addressed by my patch:
[PATCH] drm/gpuvm: Fix kernel-doc formatting and typo in
drm_gpuvm_sm_map_exec_lock
Link: https://lore.kernel.org/lkml/20250803092622.27532-1-reddybalavignesh9979@gmail.com/
The patch inserts the required directive and corrects the return-value typo.
I have verified this.
Could anyone please pick this up or keep it queued, so
warnings disappear from -next.
Thanks!
Bala Vignesh
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: linux-next: build warnings after merge of the drm-misc-fixes tree
2025-08-20 18:35 ` Bala-Vignesh-Reddy
@ 2025-08-21 3:50 ` Bagas Sanjaya
0 siblings, 0 replies; 5+ messages in thread
From: Bagas Sanjaya @ 2025-08-21 3:50 UTC (permalink / raw)
To: Bala-Vignesh-Reddy
Cc: dakr, dri-devel, intel-gfx, linux-kernel, linux-next, rampxxxx,
robdclark, robin.clark, seanpaul, sfr, simona.vetter
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
On Thu, Aug 21, 2025 at 12:05:07AM +0530, Bala-Vignesh-Reddy wrote:
> Hi all,
>
> Those htmldocs warnings come from missing Sphinx markup in
> `drm_gpuvm_sm_map_exec_lock()`.
>
> This is already addressed by my patch:
>
> [PATCH] drm/gpuvm: Fix kernel-doc formatting and typo in
> drm_gpuvm_sm_map_exec_lock
>
> Link: https://lore.kernel.org/lkml/20250803092622.27532-1-reddybalavignesh9979@gmail.com/
>
> The patch inserts the required directive and corrects the return-value typo.
> I have verified this.
>
> Could anyone please pick this up or keep it queued, so
> warnings disappear from -next.
I think this has been already addressed by Javier's patch and mine (see the
full thread). However, one of them must be in mainline.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2025-08-21 3:50 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-18 2:38 linux-next: build warnings after merge of the drm-misc-fixes tree Stephen Rothwell
2025-08-18 5:56 ` Bagas Sanjaya
2025-08-18 8:24 ` Danilo Krummrich
2025-08-20 18:35 ` Bala-Vignesh-Reddy
2025-08-21 3:50 ` Bagas Sanjaya
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).