All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>
Cc: dakr@kernel.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, rampxxxx@gmail.com,
	robdclark@gmail.com, robin.clark@oss.qualcomm.com,
	seanpaul@chromium.org, sfr@canb.auug.org.au,
	simona.vetter@ffwll.ch
Subject: Re: linux-next: build warnings after merge of the drm-misc-fixes tree
Date: Thu, 21 Aug 2025 10:50:15 +0700	[thread overview]
Message-ID: <aKaXd-du1Zp9soSZ@archie.me> (raw)
In-Reply-To: <20250820183507.84200-1-reddybalavignesh9979@gmail.com>

[-- 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 --]

      reply	other threads:[~2025-08-21  3:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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=aKaXd-du1Zp9soSZ@archie.me \
    --to=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=reddybalavignesh9979@gmail.com \
    --cc=robdclark@gmail.com \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=seanpaul@chromium.org \
    --cc=sfr@canb.auug.org.au \
    --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.