From: Daniel Vetter <daniel@ffwll.ch>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: daniel.vetter@ffwll.ch,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ttm: fix kerneldoc for ttm_lru_bulk_move
Date: Wed, 13 Apr 2022 11:22:34 +0200 [thread overview]
Message-ID: <YlaWWiNRCcc0FVY3@phenom.ffwll.local> (raw)
In-Reply-To: <20220413091242.638413-1-christian.koenig@amd.com>
On Wed, Apr 13, 2022 at 11:12:42AM +0200, Christian König wrote:
> Update the kerneldoc for the members as well.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> Fixes: b0e2c9ea5afc ("drm/ttm: allow bulk moves for all domains")
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
> include/drm/ttm/ttm_resource.h | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/include/drm/ttm/ttm_resource.h b/include/drm/ttm/ttm_resource.h
> index 314f73de4280..f82fee18c07f 100644
> --- a/include/drm/ttm/ttm_resource.h
> +++ b/include/drm/ttm/ttm_resource.h
> @@ -215,8 +215,7 @@ struct ttm_lru_bulk_move_pos {
> /**
> * struct ttm_lru_bulk_move
> *
> - * @tt: first/last lru entry for resources in the TT domain
> - * @vram: first/last lru entry for resources in the VRAM domain
> + * @pos: first/last lru entry for resources in the each domain/priority
> *
> * Container for the current bulk move state. Should be used with
> * ttm_lru_bulk_move_init() and ttm_bo_set_bulk_move().
> --
> 2.25.1
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2022-04-13 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 9:12 [PATCH] drm/ttm: fix kerneldoc for ttm_lru_bulk_move Christian König
2022-04-13 9:22 ` Daniel Vetter [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=YlaWWiNRCcc0FVY3@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).