dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	David Airlie <airlied@redhat.com>
Cc: Mark Brown <broonie@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Alex Deucher <alexander.deucher@amd.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Aurabindo Pillai <aurabindo.pillai@amd.com>
Subject: Re: linux-next: build failure after merge of the drm tree
Date: Thu, 6 Oct 2022 12:25:05 -0400	[thread overview]
Message-ID: <a02ce536-0f45-212d-cb97-ae6aae6c567c@amd.com> (raw)
In-Reply-To: <20221006191245.11bb0e2c@canb.auug.org.au>

On 2022-10-06 04:12, Stephen Rothwell wrote:
> Hi all,
> 
> On Thu, 6 Oct 2022 09:28:10 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> I have applied the following hack for today:
>>
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Thu, 6 Oct 2022 09:14:26 +1100
>> Subject: [PATCH] fix up for drivers/gpu/drm/amd/display/dc/core/dc_stream.c
>>
>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> ---
>>   drivers/gpu/drm/amd/display/dc/core/dc_stream.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_stream.c b/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
>> index ae13887756bf..a5da787b7876 100644
>> --- a/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
>> +++ b/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
>> @@ -520,9 +520,9 @@ bool dc_stream_remove_writeback(struct dc *dc,
>>   	}
>>   
>>   	/* remove writeback info for disabled writeback pipes from stream */
>> -	for (i = 0, j = 0; i < stream->num_wb_info && j < MAX_DWB_PIPES; i++) {
>> +	for (i = 0, j = 0; i < stream->num_wb_info && i < MAX_DWB_PIPES; i++) {
>>   		if (stream->writeback_info[i].wb_enabled) {
>> -			if (i != j)
>> +			if ((j >= 0) && (j < i))
>>   				/* trim the array */
>>   				stream->writeback_info[j] = stream->writeback_info[i];
>>   			j++;
> 
> This works as well, and (in my opinion) is better:

I can confirm that this fix works on GCC 9.4, as well.

> 
> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_stream.c b/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
> index ae13887756bf..fb6222d4c430 100644
> --- a/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
> +++ b/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
> @@ -499,7 +499,7 @@ bool dc_stream_remove_writeback(struct dc *dc,
>   		struct dc_stream_state *stream,
>   		uint32_t dwb_pipe_inst)
>   {
> -	int i = 0, j = 0;
> +	unsigned int i, j;
>   	if (stream == NULL) {
>   		dm_error("DC: dc_stream is NULL!\n");
>   		return false;
> @@ -520,9 +520,9 @@ bool dc_stream_remove_writeback(struct dc *dc,
>   	}
>   
>   	/* remove writeback info for disabled writeback pipes from stream */
> -	for (i = 0, j = 0; i < stream->num_wb_info && j < MAX_DWB_PIPES; i++) {
> +	for (i = 0, j = 0; i < stream->num_wb_info; i++) {
>   		if (stream->writeback_info[i].wb_enabled) {
> -			if (i != j)
> +			if (j < i)
>   				/* trim the array */
>   				stream->writeback_info[j] = stream->writeback_info[i];
>   			j++;
> 

-- 
Hamza


  parent reply	other threads:[~2022-10-06 16:24 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220930105434.111407-1-broonie@kernel.org>
2022-10-04  2:20 ` linux-next: build failure after merge of the drm tree Stephen Rothwell
2022-10-04  2:24   ` David Airlie
2022-10-04  3:05     ` Stephen Rothwell
2022-10-04 11:39       ` Mark Brown
2022-10-05 15:30         ` Alex Deucher
2022-10-05 16:45           ` Hamza Mahfooz
2022-10-05 22:28             ` Stephen Rothwell
2022-10-06  8:12               ` Stephen Rothwell
2022-10-06 13:56                 ` Alex Deucher
2022-10-06 16:52                   ` Stephen Rothwell
2022-10-06 16:25                 ` Hamza Mahfooz [this message]
2023-04-11  6:47 Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-01-19  2:12 Stephen Rothwell
2022-02-25 16:42 broonie
2022-02-28  3:46 ` Stephen Rothwell
2022-02-28  6:44 ` Hsin-Yi Wang
2022-02-28  6:48   ` Dave Airlie
2022-02-28 15:33     ` Robert Foss
2022-03-01  6:58       ` Dave Airlie
2021-08-20  2:33 Stephen Rothwell
2021-08-20  6:23 ` Masahiro Yamada
2021-09-01 21:50   ` Stephen Rothwell
2021-09-05 22:49     ` Stephen Rothwell
2021-09-06  7:34       ` Daniel Vetter
2021-09-08  3:13         ` Masahiro Yamada
2021-09-08  9:07           ` Daniel Vetter
2021-04-09  3:36 Stephen Rothwell
2021-01-08  0:55 Stephen Rothwell
2021-01-08  1:25 ` Stephen Rothwell
2021-01-10 23:56   ` Stephen Rothwell
2021-01-18  0:59     ` Stephen Rothwell
2021-01-18  1:06       ` Dave Airlie
2021-01-20 12:12         ` Daniel Vetter
2021-01-20 20:44           ` Stephen Rothwell
2020-12-09  1:53 Stephen Rothwell
2020-09-28  3:54 Stephen Rothwell
     [not found] ` <20200928060427.GA15041@lst.de>
2020-09-28  6:08   ` Dave Airlie
2020-09-28 10:15   ` Paul Cercueil
     [not found]     ` <20200928113415.GA555@lst.de>
2020-09-28 11:46       ` Paul Cercueil
     [not found]         ` <20200928121002.GA3219@lst.de>
2020-09-28 13:31           ` Paul Cercueil
     [not found]             ` <20200930090252.GA9357@lst.de>
2020-09-30 13:33               ` Paul Cercueil
     [not found]                 ` <20200930161124.GA6859@lst.de>
2020-09-30 16:39                   ` Paul Cercueil
     [not found]                     ` <20200930164023.GA8645@lst.de>
2020-09-30 16:45                       ` Paul Cercueil
2020-05-08  4:29 Stephen Rothwell
2019-11-05  2:54 Stephen Rothwell
2019-11-05  2:54 ` Stephen Rothwell
2019-10-10  0:22 Stephen Rothwell
2019-07-08  4:48 Stephen Rothwell
2019-04-26  2:17 Stephen Rothwell
2018-05-16  6:53 Stephen Rothwell
2018-05-16  8:09 ` Oded Gabbay
2018-05-17  5:00   ` Dave Airlie
2018-03-13  5:46 Stephen Rothwell
2018-01-02  1:48 Stephen Rothwell
2017-03-20  0:51 Stephen Rothwell
2017-03-20  8:03 ` Daniel Vetter
2017-03-20  8:05   ` Daniel Vetter
2016-07-15  3:40 Stephen Rothwell
2016-07-15  4:32 ` Sedat Dilek
2016-04-28  1:57 Stephen Rothwell
2016-04-28  8:11 ` Jani Nikula

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=a02ce536-0f45-212d-cb97-ae6aae6c567c@amd.com \
    --to=hamza.mahfooz@amd.com \
    --cc=airlied@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=aurabindo.pillai@amd.com \
    --cc=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).