Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Aurabindo Pillai <aurabindo.pillai@amd.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	igt-dev@lists.freedesktop.org, hersenxs.wu@amd.com,
	Ashutosh Dixit <ashutosh.dixit@intel.com>,
	Petri Latvala <adrinael@adrinael.net>
Subject: Re: [igt-dev] [PATCH v4] tests/amdgpu: Fix build error due to external file include
Date: Tue, 22 Aug 2023 16:57:54 -0400	[thread overview]
Message-ID: <a5c62ee7-b17b-4d03-83ff-e8e579009679@amd.com> (raw)
In-Reply-To: <20230822204709.zuoxonzyn5ij42jy@kamilkon-desk.igk.intel.com>



On 2023-08-22 16:47, Kamil Konieczny wrote:
> Hi Aurabindo,
> 
> On 2023-08-22 at 16:18:33 -0400, Aurabindo Pillai wrote:
>> Remove the external file include that causes build error
>> on certain systems configured in the CI.
>>
>> Signed-off-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
>> ---
>>   tests/amdgpu/amd_odm.c | 1 -
>>   1 file changed, 1 deletion(-)
>>
>> diff --git a/tests/amdgpu/amd_odm.c b/tests/amdgpu/amd_odm.c
>> index 2781ad1c2..839f2de3f 100644
>> --- a/tests/amdgpu/amd_odm.c
>> +++ b/tests/amdgpu/amd_odm.c
>> @@ -5,7 +5,6 @@
>>   
>>   #include <fcntl.h>
>>   #include <stdio.h>
>> -#include <xf86drmMode.h>
> 
> Acked-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> 
> Will this test work without xf86drmMode.h?
> If it is kms test you may just include igt_kms.h but first
> apply fix (or revert).

Yes, looks like IGT already includes all the necessary headers.

> 
> Regards,
> Kamil
> 
>>   
>>   #include "igt.h"
>>   #include "igt_amd.h"
>> -- 
>> 2.41.0
>>

-- 
--

Thanks & Regards,
Jay

  reply	other threads:[~2023-08-22 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 20:18 [igt-dev] [PATCH v4] tests/amdgpu: Fix build error due to external file include Aurabindo Pillai
2023-08-22 20:47 ` Kamil Konieczny
2023-08-22 20:57   ` Aurabindo Pillai [this message]
2023-08-22 23:04 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork

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=a5c62ee7-b17b-4d03-83ff-e8e579009679@amd.com \
    --to=aurabindo.pillai@amd.com \
    --cc=adrinael@adrinael.net \
    --cc=ashutosh.dixit@intel.com \
    --cc=hersenxs.wu@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.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