From: Alex Deucher <alexdeucher@gmail.com>
To: Nayan Deshmukh <nayan26deshmukh@gmail.com>
Cc: Christian Koenig <christian.koenig@amd.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/scheduler: fix function name prefix in comments
Date: Thu, 17 May 2018 14:37:21 -0400 [thread overview]
Message-ID: <CADnq5_Mutju73uqDfx8t1MNVTk33aJEgTYSYyjWuw1snRzicJw@mail.gmail.com> (raw)
In-Reply-To: <20180516132418.11034-1-nayan26deshmukh@gmail.com>
On Wed, May 16, 2018 at 9:24 AM, Nayan Deshmukh
<nayan26deshmukh@gmail.com> wrote:
> That got missed while moving the files outside of amdgpu.
>
> Signed-off-by: Nayan Deshmukh <nayan26deshmukh@gmail.com>
> Reviewed-by: Christian König <christian.koenig@amd.com>
Applied. thanks!
Alex
> ---
> drivers/gpu/drm/scheduler/sched_fence.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/scheduler/sched_fence.c b/drivers/gpu/drm/scheduler/sched_fence.c
> index 69aab086b913..786b47f15783 100644
> --- a/drivers/gpu/drm/scheduler/sched_fence.c
> +++ b/drivers/gpu/drm/scheduler/sched_fence.c
> @@ -87,7 +87,7 @@ static bool drm_sched_fence_enable_signaling(struct dma_fence *f)
> }
>
> /**
> - * amd_sched_fence_free - free up the fence memory
> + * drm_sched_fence_free - free up the fence memory
> *
> * @rcu: RCU callback head
> *
> @@ -103,7 +103,7 @@ static void drm_sched_fence_free(struct rcu_head *rcu)
> }
>
> /**
> - * amd_sched_fence_release_scheduled - callback that fence can be freed
> + * drm_sched_fence_release_scheduled - callback that fence can be freed
> *
> * @fence: fence
> *
> @@ -118,7 +118,7 @@ static void drm_sched_fence_release_scheduled(struct dma_fence *f)
> }
>
> /**
> - * amd_sched_fence_release_finished - drop extra reference
> + * drm_sched_fence_release_finished - drop extra reference
> *
> * @f: fence
> *
> --
> 2.14.3
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-05-17 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 13:03 [PATCH] drm/scheduler: fix function name prefix in comments Nayan Deshmukh
2018-05-16 13:07 ` Christian König
2018-05-16 13:24 ` Nayan Deshmukh
2018-05-17 18:37 ` Alex Deucher [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=CADnq5_Mutju73uqDfx8t1MNVTk33aJEgTYSYyjWuw1snRzicJw@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=nayan26deshmukh@gmail.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;
as well as URLs for NNTP newsgroup(s).