Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Aurabindo Pillai <aurabindo.pillai@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: hersenxs.wu@amd.com
Subject: [igt-dev] [PATCH i-g-t v2 1/5] lib/amdgpu: Remove unused struct
Date: Fri, 3 Nov 2023 14:22:26 -0400	[thread overview]
Message-ID: <20231103182230.1039191-2-aurabindo.pillai@amd.com> (raw)
In-Reply-To: <20231103182230.1039191-1-aurabindo.pillai@amd.com>

dim2d has no references within AMDGPU tests, so remove it

Signed-off-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
---
 lib/igt_amd.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/lib/igt_amd.c b/lib/igt_amd.c
index 84c6d7545..f0fbe97ef 100644
--- a/lib/igt_amd.c
+++ b/lib/igt_amd.c
@@ -45,11 +45,6 @@
 #define Y6 64
 #define Y7 128
 
-struct dim2d
-{
-    int w;
-    int h;
-};
 
 uint32_t igt_amd_create_bo(int fd, uint64_t size)
 {
-- 
2.39.2

  reply	other threads:[~2023-11-03 18:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 18:22 [igt-dev] [PATCH i-g-t v2 0/5] Add a new test for Sub-viewport Aurabindo Pillai
2023-11-03 18:22 ` Aurabindo Pillai [this message]
2023-11-08  6:38   ` [igt-dev] [PATCH i-g-t v2 1/5] lib/amdgpu: Remove unused struct Alex Hung
2023-11-03 18:22 ` [igt-dev] [PATCH i-g-t v2 2/5] llib/amd: Update function documentation Aurabindo Pillai
2023-11-08  6:38   ` Alex Hung
2023-11-03 18:22 ` [igt-dev] [PATCH i-g-t v2 3/5] lib/amd: improve readablity for MALL capability check Aurabindo Pillai
2023-11-08  6:39   ` Alex Hung
2023-11-03 18:22 ` [igt-dev] [PATCH i-g-t v2 4/5] lib/amd: Add check for SubVP feature status Aurabindo Pillai
2023-11-08  6:40   ` Alex Hung
2023-11-03 18:22 ` [igt-dev] [PATCH i-g-t v2 5/5] test/amdgpu: Add test for Sub-viewport Aurabindo Pillai
2023-11-03 18:25   ` Aurabindo Pillai
2023-11-08  6:41   ` Alex Hung
2023-11-03 19:31 ` [igt-dev] ✗ Fi.CI.BAT: failure for Add a new " Patchwork
2023-11-06 20:00 ` [igt-dev] [PATCH i-g-t v2 0/5] " Aurabindo Pillai

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=20231103182230.1039191-2-aurabindo.pillai@amd.com \
    --to=aurabindo.pillai@amd.com \
    --cc=hersenxs.wu@amd.com \
    --cc=igt-dev@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