From: Nirmoy <nirmodas@amd.com>
To: James Zhu <James.Zhu@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu/vcn3.0: fix compilation warning
Date: Wed, 25 Nov 2020 15:33:05 +0100 [thread overview]
Message-ID: <4b52f025-8126-ecb9-91df-db7bbb64fa23@amd.com> (raw)
In-Reply-To: <1606313384-7808-1-git-send-email-James.Zhu@amd.com>
Reviewed-by: Nirmoy Das <nirmoy.das@amd.com>
On 11/25/20 3:09 PM, James Zhu wrote:
> Fixed warning: no previous prototype.
>
> Signed-off-by: James Zhu <James.Zhu@amd.com>
> Reported-by: kernel test robot <lkp@intel.com>
> ---
> drivers/gpu/drm/amd/amdgpu/vcn_v3_0.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v3_0.c b/drivers/gpu/drm/amd/amdgpu/vcn_v3_0.c
> index 71e10bf..0c97322 100644
> --- a/drivers/gpu/drm/amd/amdgpu/vcn_v3_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/vcn_v3_0.c
> @@ -1701,7 +1701,7 @@ static void vcn_v3_0_dec_ring_set_wptr(struct amdgpu_ring *ring)
> }
> }
>
> -void vcn_v3_0_dec_sw_ring_emit_fence(struct amdgpu_ring *ring, u64 addr,
> +static void vcn_v3_0_dec_sw_ring_emit_fence(struct amdgpu_ring *ring, u64 addr,
> u64 seq, uint32_t flags)
> {
> WARN_ON(flags & AMDGPU_FENCE_FLAG_64BIT);
> @@ -1713,12 +1713,12 @@ void vcn_v3_0_dec_sw_ring_emit_fence(struct amdgpu_ring *ring, u64 addr,
> amdgpu_ring_write(ring, VCN_DEC_SW_CMD_TRAP);
> }
>
> -void vcn_v3_0_dec_sw_ring_insert_end(struct amdgpu_ring *ring)
> +static void vcn_v3_0_dec_sw_ring_insert_end(struct amdgpu_ring *ring)
> {
> amdgpu_ring_write(ring, VCN_DEC_SW_CMD_END);
> }
>
> -void vcn_v3_0_dec_sw_ring_emit_ib(struct amdgpu_ring *ring,
> +static void vcn_v3_0_dec_sw_ring_emit_ib(struct amdgpu_ring *ring,
> struct amdgpu_job *job,
> struct amdgpu_ib *ib,
> uint32_t flags)
> @@ -1732,7 +1732,7 @@ void vcn_v3_0_dec_sw_ring_emit_ib(struct amdgpu_ring *ring,
> amdgpu_ring_write(ring, ib->length_dw);
> }
>
> -void vcn_v3_0_dec_sw_ring_emit_reg_wait(struct amdgpu_ring *ring, uint32_t reg,
> +static void vcn_v3_0_dec_sw_ring_emit_reg_wait(struct amdgpu_ring *ring, uint32_t reg,
> uint32_t val, uint32_t mask)
> {
> amdgpu_ring_write(ring, VCN_DEC_SW_CMD_REG_WAIT);
> @@ -1741,7 +1741,7 @@ void vcn_v3_0_dec_sw_ring_emit_reg_wait(struct amdgpu_ring *ring, uint32_t reg,
> amdgpu_ring_write(ring, val);
> }
>
> -void vcn_v3_0_dec_sw_ring_emit_vm_flush(struct amdgpu_ring *ring,
> +static void vcn_v3_0_dec_sw_ring_emit_vm_flush(struct amdgpu_ring *ring,
> uint32_t vmid, uint64_t pd_addr)
> {
> struct amdgpu_vmhub *hub = &ring->adev->vmhub[ring->funcs->vmhub];
> @@ -1756,7 +1756,7 @@ void vcn_v3_0_dec_sw_ring_emit_vm_flush(struct amdgpu_ring *ring,
> vcn_v3_0_dec_sw_ring_emit_reg_wait(ring, data0, data1, mask);
> }
>
> -void vcn_v3_0_dec_sw_ring_emit_wreg(struct amdgpu_ring *ring, uint32_t reg, uint32_t val)
> +static void vcn_v3_0_dec_sw_ring_emit_wreg(struct amdgpu_ring *ring, uint32_t reg, uint32_t val)
> {
> amdgpu_ring_write(ring, VCN_DEC_SW_CMD_REG_WRITE);
> amdgpu_ring_write(ring, reg << 2);
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-11-25 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:09 [PATCH] drm/amdgpu/vcn3.0: fix compilation warning James Zhu
2020-11-25 14:33 ` Nirmoy [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=4b52f025-8126-ecb9-91df-db7bbb64fa23@amd.com \
--to=nirmodas@amd.com \
--cc=James.Zhu@amd.com \
--cc=amd-gfx@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