From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Loïc Molinari" <loic.molinari@collabora.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI Devel Mailing List <dri-devel@lists.freedesktop.org>,
Intel Graphics Mailing List <intel-gfx@lists.freedesktop.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Collabora Kernel Mailing List <kernel@collabora.com>
Subject: Re: [PATCH] drm/gem: Fix kerneldoc warnings
Date: Thu, 18 Dec 2025 11:09:37 +0100 [thread overview]
Message-ID: <20251218110937.2d1a0c7d@fedora> (raw)
In-Reply-To: <20251217172404.31216-1-loic.molinari@collabora.com>
On Wed, 17 Dec 2025 18:24:04 +0100
Loïc Molinari <loic.molinari@collabora.com> wrote:
> Fix incorrect parameters in drm_gem_shmem_init() and missing " *" on
> empty lines in drm_gem_get_huge_mnt().
>
> Signed-off-by: Loïc Molinari <loic.molinari@collabora.com>
Queued to drm-misc-next.
> ---
> drivers/gpu/drm/drm_gem_shmem_helper.c | 7 +++++--
> include/drm/drm_gem.h | 4 ++--
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_gem_shmem_helper.c b/drivers/gpu/drm/drm_gem_shmem_helper.c
> index 29174ab58ff3..fbd1164174b0 100644
> --- a/drivers/gpu/drm/drm_gem_shmem_helper.c
> +++ b/drivers/gpu/drm/drm_gem_shmem_helper.c
> @@ -94,9 +94,12 @@ static int __drm_gem_shmem_init(struct drm_device *dev, struct drm_gem_shmem_obj
> }
>
> /**
> - * drm_gem_shmem_init - Initialize an allocated object.
> + * drm_gem_shmem_init - Initialize an allocated object of the given size
> * @dev: DRM device
> - * @obj: The allocated shmem GEM object.
> + * @shmem: shmem GEM object to initialize
> + * @size: Size of the object to initialize
> + *
> + * This function initializes an allocated shmem GEM object.
> *
> * Returns:
> * 0 on success, or a negative error code on failure.
> diff --git a/include/drm/drm_gem.h b/include/drm/drm_gem.h
> index f4da8ed0d630..86f5846154f7 100644
> --- a/include/drm/drm_gem.h
> +++ b/include/drm/drm_gem.h
> @@ -508,11 +508,11 @@ static inline int drm_gem_huge_mnt_create(struct drm_device *dev,
> /**
> * drm_gem_get_huge_mnt - Get the huge tmpfs mountpoint used by a DRM device
> * @dev: DRM device
> -
> + *
> * This function gets the huge tmpfs mountpoint used by DRM device @dev. A huge
> * tmpfs mountpoint is used instead of `shm_mnt` after a successful call to
> * drm_gem_huge_mnt_create() when CONFIG_TRANSPARENT_HUGEPAGE is enabled.
> -
> + *
> * Returns:
> * The huge tmpfs mountpoint in use, NULL otherwise.
> */
prev parent reply other threads:[~2025-12-18 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 17:24 [PATCH] drm/gem: Fix kerneldoc warnings Loïc Molinari
2025-12-17 18:09 ` Randy Dunlap
2025-12-18 9:00 ` Boris Brezillon
2025-12-18 10:09 ` Boris Brezillon [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=20251218110937.2d1a0c7d@fedora \
--to=boris.brezillon@collabora.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=loic.molinari@collabora.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=simona@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox