All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Sonny Jiang <sonny.jiang@amd.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] tests/amdgpu/vcn: clean abundant codes
Date: Fri, 22 Jan 2021 10:23:09 -0500	[thread overview]
Message-ID: <CADnq5_O-egBCuR8OC1u4-5uPy3wuUmSmV4jn6XYtUECLkyzkVA@mail.gmail.com> (raw)
In-Reply-To: <20210122150439.15911-1-sonny.jiang@amd.com>

Please open a libdrm MR for libdrm updates.

Alex

On Fri, Jan 22, 2021 at 10:05 AM Sonny Jiang <sonny.jiang@amd.com> wrote:
>
> Remove useless codes.
>
> Signed-off-by: Sonny Jiang <sonny.jiang@amd.com>
> ---
>  tests/amdgpu/vcn_tests.c | 2 --
>  1 file changed, 2 deletions(-)
>
> diff --git a/tests/amdgpu/vcn_tests.c b/tests/amdgpu/vcn_tests.c
> index 0f5b4241..1ca66297 100644
> --- a/tests/amdgpu/vcn_tests.c
> +++ b/tests/amdgpu/vcn_tests.c
> @@ -102,8 +102,6 @@ CU_BOOL suite_vcn_tests_enable(void)
>                 return CU_FALSE;
>
>         family_id = device_handle->info.family_id;
> -       chip_rev = device_handle->info.chip_rev;
> -       chip_id = device_handle->info.chip_external_rev;
>         asic_id = device_handle->info.asic_id;
>         chip_rev = device_handle->info.chip_rev;
>         chip_id = device_handle->info.chip_external_rev;
> --
> 2.25.1
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2021-01-22 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 15:04 [PATCH] tests/amdgpu/vcn: clean abundant codes Sonny Jiang
2021-01-22 15:06 ` Christian König
2021-01-22 15:23 ` 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_O-egBCuR8OC1u4-5uPy3wuUmSmV4jn6XYtUECLkyzkVA@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=sonny.jiang@amd.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 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.