From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/ttm: fix i915_ttm_to_gem() kernel-doc
Date: Thu, 4 May 2023 13:02:12 +0200 [thread overview]
Message-ID: <97b8773e-f584-8d0f-b6dd-77e6194f5846@linux.intel.com> (raw)
In-Reply-To: <20230504092320.1787627-1-jani.nikula@intel.com>
On 5/4/2023 11:23 AM, Jani Nikula wrote:
> drivers/gpu/drm/i915/gem/i915_gem_ttm.h:50: warning: Function parameter or member 'bo' not described in 'i915_ttm_to_gem'
>
> v2: Fix return value documentation while at it (Rodrigo)
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_ttm.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.h b/drivers/gpu/drm/i915/gem/i915_gem_ttm.h
> index f8f6bed1b297..67347e62e29b 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.h
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.h
> @@ -42,8 +42,9 @@ static inline bool i915_ttm_is_ghost_object(struct ttm_buffer_object *bo)
> /**
> * i915_ttm_to_gem - Convert a struct ttm_buffer_object to an embedding
> * struct drm_i915_gem_object.
> + * @bo: Pointer to the ttm buffer object
> *
> - * Return: Pointer to the embedding struct ttm_buffer_object.
> + * Return: Pointer to the embedding struct drm_i915_gem_object.
> */
> static inline struct drm_i915_gem_object *
> i915_ttm_to_gem(struct ttm_buffer_object *bo)
next prev parent reply other threads:[~2023-05-04 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 9:23 [Intel-gfx] [PATCH v2] drm/i915/ttm: fix i915_ttm_to_gem() kernel-doc Jani Nikula
2023-05-04 10:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-05-04 11:02 ` Das, Nirmoy [this message]
2023-05-12 7:23 ` [Intel-gfx] [PATCH v2] " Jani Nikula
2023-05-04 12:51 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
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=97b8773e-f584-8d0f-b6dd-77e6194f5846@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@intel.com \
/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