From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Simona Vetter <simona.vetter@ffwll.ch>,
Rob Clark <robdclark@gmail.com>,
Sean Paul <seanpaul@chromium.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Danilo Krummrich <dakr@kernel.org>,
Javier Garcia <rampxxxx@gmail.com>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the drm-misc-fixes tree
Date: Mon, 18 Aug 2025 12:38:53 +1000 [thread overview]
Message-ID: <20250818123853.51aa3bc4@canb.auug.org.au> (raw)
[-- 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 --]
next reply other threads:[~2025-08-18 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:38 Stephen Rothwell [this message]
2025-08-18 5:56 ` linux-next: build warnings after merge of the drm-misc-fixes tree Bagas Sanjaya
2025-08-18 8:24 ` Danilo Krummrich
2025-08-20 18:35 ` Bala-Vignesh-Reddy
2025-08-21 3:50 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250818123853.51aa3bc4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bagasdotme@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rampxxxx@gmail.com \
--cc=robdclark@gmail.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=seanpaul@chromium.org \
--cc=simona.vetter@ffwll.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.