From: "Russell, Kent" <Kent.Russell@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: RE: [PATCH 2/2] drm/amdgpu: fix documentation warning
Date: Tue, 28 Jun 2022 13:34:40 +0000 [thread overview]
Message-ID: <DM5PR12MB13086060C2D6A3DEC925377985B89@DM5PR12MB1308.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CADnq5_ML3Hu-fhFigqUHGnArKHY1-n2z=_dzYKkg5kHeXNSu5g@mail.gmail.com>
[AMD Official Use Only - General]
Not sure why no one responded, but this is something even I can RB.
Reviewed-by: Kent Russell <kent.russell@amd.com>
> -----Original Message-----
> From: amd-gfx <amd-gfx-bounces@lists.freedesktop.org> On Behalf Of Alex
> Deucher
> Sent: Monday, June 27, 2022 5:41 PM
> To: Deucher, Alexander <Alexander.Deucher@amd.com>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>; amd-gfx list <amd-
> gfx@lists.freedesktop.org>
> Subject: Re: [PATCH 2/2] drm/amdgpu: fix documentation warning
>
> Ping?
>
> On Thu, Jun 23, 2022 at 12:41 PM Alex Deucher <alexander.deucher@amd.com>
> wrote:
> >
> > Fixes this issue:
> > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:5094: warning: expecting
> prototype for amdgpu_device_gpu_recover_imp(). Prototype was for
> amdgpu_device_gpu_recover() instead
> >
> > Fixes: cf727044144d ("drm/amdgpu: Rename
> amdgpu_device_gpu_recover_imp back to amdgpu_device_gpu_recover")
> > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > ---
> > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> > index f2a4c268ac72..6c0fbc662b3a 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> > @@ -5079,7 +5079,7 @@ static inline void
> amdggpu_device_stop_pedning_resets(struct amdgpu_device *adev
> >
> >
> > /**
> > - * amdgpu_device_gpu_recover_imp - reset the asic and recover scheduler
> > + * amdgpu_device_gpu_recover - reset the asic and recover scheduler
> > *
> > * @adev: amdgpu_device pointer
> > * @job: which job trigger hang
> > --
> > 2.35.3
> >
next prev parent reply other threads:[~2022-06-28 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 16:41 [PATCH 1/2] drm/amdgpu/display: drop set but unused variable Alex Deucher
2022-06-23 16:41 ` [PATCH 2/2] drm/amdgpu: fix documentation warning Alex Deucher
2022-06-27 21:40 ` Alex Deucher
2022-06-28 13:34 ` Russell, Kent [this message]
2022-06-23 21:36 ` [PATCH 1/2] drm/amdgpu/display: drop set but unused variable Harry Wentland
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=DM5PR12MB13086060C2D6A3DEC925377985B89@DM5PR12MB1308.namprd12.prod.outlook.com \
--to=kent.russell@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=sfr@canb.auug.org.au \
/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.