From: "Danilo Krummrich" <dakr@kernel.org>
To: "Ankan Biswas" <spyjetfayed@gmail.com>
Cc: <bbrezillon@kernel.org>, <himal.prasad.ghimiray@intel.com>,
<matt.coster@imgtec.com>, <robin.clark@oss.qualcomm.com>,
<matthew.brost@intel.com>, <aliceryhl@google.com>,
<thomas.hellstrom@linux.intel.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <simona@ffwll.ch>,
<skhan@linuxfoundation.org>, <khalid@kernel.org>,
<david.hunter.linux@gmail.com>, <linux-kernel@vger.kernel.org>,
<linux-kernel-mentees@lists.linux.dev>,
<dri-devel@lists.freedesktop.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [PATCH v3] drm/gpuvm: Fix kernel-doc warning for drm_gpuvm_map_req.map
Date: Wed, 15 Oct 2025 18:39:01 +0200 [thread overview]
Message-ID: <DDJ1LC1XM765.33V1SPVZAIKP5@kernel.org> (raw)
In-Reply-To: <20251015152543.24368-1-spyjetfayed@gmail.com>
On Wed Oct 15, 2025 at 5:20 PM CEST, Ankan Biswas wrote:
> The kernel-doc for struct drm_gpuvm_map_req.map was added as '@op_map'
> instead of '@map', leading to this warning during htmldocs build:
>
> WARNING: include/drm/drm_gpuvm.h:1083 struct member 'map' not described in 'drm_gpuvm_map_req'
>
> Fixes: 000a45dce7ad ("drm/gpuvm: Pass map arguments through a struct")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/all/20250821133539.03aa298e@canb.auug.org.au/
> Signed-off-by: Ankan Biswas <spyjetfayed@gmail.com>
Applied to drm-misc-fixes, thanks!
next prev parent reply other threads:[~2025-10-15 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 15:20 [PATCH v3] drm/gpuvm: Fix kernel-doc warning for drm_gpuvm_map_req.map Ankan Biswas
2025-10-15 16:39 ` Danilo Krummrich [this message]
2025-10-15 16:41 ` Matt Coster
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=DDJ1LC1XM765.33V1SPVZAIKP5@kernel.org \
--to=dakr@kernel.org \
--cc=aliceryhl@google.com \
--cc=bbrezillon@kernel.org \
--cc=david.hunter.linux@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=khalid@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matt.coster@imgtec.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sfr@canb.auug.org.au \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=spyjetfayed@gmail.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
/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.