[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e0252635-4dc4-483a-911a-fee5a36c19c3@kernel.org>
Date: Fri, 12 Sep 2025 23:27:34 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Documentation <linux-doc@...r.kernel.org>,
Linux DRI Development <dri-devel@...ts.freedesktop.org>,
Matthew Brost <matthew.brost@...el.com>,
Thomas Hellström <thomas.hellstrom@...ux.intel.com>,
Alice Ryhl <aliceryhl@...gle.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
Javier Garcia <rampxxxx@...il.com>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
Antonino Maniscalco <antomani103@...il.com>,
Rob Clark <robin.clark@....qualcomm.com>,
Randy Dunlap <rdunlap@...radead.org>, Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH] Revert "drm: Add directive to format code in comment"
On 9/12/25 3:06 PM, Bagas Sanjaya wrote:
> Commit 6cc44e9618f03f ("drm: Add directive to format code in comment")
> fixes original Sphinx indentation warning as introduced in
> 471920ce25d50b ("drm/gpuvm: Add locking helpers"), by means of using
> code-block:: directive. It semantically conflicts with earlier
> bb324f85f72284 ("drm/gpuvm: Wrap drm_gpuvm_sm_map_exec_lock() expected
> usage in literal code block") that did the same using double colon
> syntax instead. These duplicated literal code block directives causes
> the original warnings not being fixed.
>
> Revert 6cc44e9618f03f to keep things rolling without these warnings.
>
> Fixes: 6cc44e9618f0 ("drm: Add directive to format code in comment")
> Fixes: 471920ce25d5 ("drm/gpuvm: Add locking helpers")
> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
Need me to pick this one up? Otherwise,
Acked-by: Danilo Krummrich <dakr@...nel.org>
Powered by blists - more mailing lists