dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Jiabing Wan <wanjiabing@vivo.com>,
	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Cc: Anson Jacob <Anson.Jacob@amd.com>, Eric Yang <Eric.Yang2@amd.com>,
	Wesley Chalmers <Wesley.Chalmers@amd.com>,
	Leo Li <sunpeng.li@amd.com>,
	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
	dri-devel@lists.freedesktop.org,
	Chiawen Huang <chiawen.huang@amd.com>,
	linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	Meenakshikumar Somasundaram <meenakshikumar.somasundaram@amd.com>,
	David Airlie <airlied@linux.ie>,
	Aurabindo Pillai <aurabindo.pillai@amd.com>,
	Alvin Lee <alvin.lee2@amd.com>, Wayne Lin <Wayne.Lin@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	kael_w@yeah.net,
	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Subject: Re: [PATCH] drm/amd/display: Remove duplicate include of hubp.h
Date: Thu, 29 Apr 2021 17:21:36 +0200	[thread overview]
Message-ID: <72012864-b24a-8697-def3-99d91f3bf89a@amd.com> (raw)
In-Reply-To: <AB*ANgDFDju3UB4GeQss-4rk.3.1619709495070.Hmail.wanjiabing@vivo.com>

Well if you are bored we quite often have the problem of unused fields 
in structures.

If your robot could find fields which are never read, that would be 
quite helpful I think.

There probably will be a lot of false positives for things like padding, 
but maybe that yields something.

Christian.

Am 29.04.21 um 17:18 schrieb Jiabing Wan:
>   
>> Is your robot public available?
> Sorry, I started to write the robot just one week ago.
> It is not strong and complete enough so it is not public available now.
> But I am still working on it. If complete, it can be public available.
>
> In fact, this patch is catched by the script called checkinclude.pl
> in linux/script. The robot just run the script and catch it ;).
>
> There will be more scripts in the robot and I think
> it will be public available soon.
>
>> btw, applied to amd-staging-drm-next.
> Thank you very much.
>
>> Thanks
>> On 04/29, Jiabing Wan wrote:
>>>   
>>>> Nice catch!
>>>>
>>>> Are you using any tool to identify this problem?
>>> Yes, I have a robot including many detecting scripts :)
>>>
>>>> Reviewed-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
>>>>
>>>> On 04/29, Wan Jiabing wrote:
>>>>> In commit 482812d56698e ("drm/amd/display: Set max TTU on
>>>>> DPG enable"), "hubp.h" was added which caused the duplicate include.
>>>>> To be on the safe side, remove the later duplicate include.
>>>>>
>>>>> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
>>>>> ---
>>>>>   drivers/gpu/drm/amd/display/dc/core/dc.c | 1 -
>>>>>   1 file changed, 1 deletion(-)
>>>>>
>>>>> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c b/drivers/gpu/drm/amd/display/dc/core/dc.c
>>>>> index 8f0a13807d05..dcaa6b1e16af 100644
>>>>> --- a/drivers/gpu/drm/amd/display/dc/core/dc.c
>>>>> +++ b/drivers/gpu/drm/amd/display/dc/core/dc.c
>>>>> @@ -58,7 +58,6 @@
>>>>>   #include "dc_link_ddc.h"
>>>>>   #include "dm_helpers.h"
>>>>>   #include "mem_input.h"
>>>>> -#include "hubp.h"
>>>>>   
>>>>>   #include "dc_link_dp.h"
>>>>>   #include "dc_dmub_srv.h"
>>>>> -- 
>>>>> 2.25.1
>>>>>
>>>> -- 
>>>> Rodrigo Siqueira
>>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsiqueira.tech%2F&amp;data=04%7C01%7Cchristian.koenig%40amd.com%7C99075b6ba68a4c6d4f9108d90b220472%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637553063002111816%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=U5VbADSJ8HJ%2Bq%2BPCGYmCuwks61s5GZtCI4n%2BdjT0LXc%3D&amp;reserved=0
>>> Yours,
>>> Wan Jiabing
>>>
>> -- 
>> Rodrigo Siqueira
>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsiqueira.tech%2F&amp;data=04%7C01%7Cchristian.koenig%40amd.com%7C99075b6ba68a4c6d4f9108d90b220472%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637553063002111816%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=U5VbADSJ8HJ%2Bq%2BPCGYmCuwks61s5GZtCI4n%2BdjT0LXc%3D&amp;reserved=0
> Yours,
> Wan Jiabing
>
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2021-04-29 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  3:04 [PATCH] drm/amd/display: Remove duplicate include of hubp.h Wan Jiabing
2021-04-29 12:05 ` Rodrigo Siqueira
2021-04-29 12:23   ` Jiabing Wan
2021-04-29 14:41     ` Rodrigo Siqueira
2021-04-29 15:18       ` Jiabing Wan
2021-04-29 15:21         ` Christian König [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=72012864-b24a-8697-def3-99d91f3bf89a@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Anson.Jacob@amd.com \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=Eric.Yang2@amd.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=Wayne.Lin@amd.com \
    --cc=Wesley.Chalmers@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=alvin.lee2@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=aurabindo.pillai@amd.com \
    --cc=chiawen.huang@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kael_w@yeah.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meenakshikumar.somasundaram@amd.com \
    --cc=nicholas.kazlauskas@amd.com \
    --cc=sunpeng.li@amd.com \
    --cc=wanjiabing@vivo.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;
as well as URLs for NNTP newsgroup(s).