[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YpTBBPVxcdJ8sn8m@kroah.com>
Date: Mon, 30 May 2022 15:05:08 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Ryan Lin <tsung-hua.lin@....com>
Cc: leon.li@....com, praful.swarnakar@....com, shirish.s@....com,
ching-shih.li@....com, Alex Deucher <alexander.deucher@....com>,
Daniel Vetter <daniel@...ll.ch>,
Nicholas Kazlauskas <nicholas.kazlauskas@....com>,
stable@...r.kernel.org, Harry Wentland <harry.wentland@....com>,
Leo Li <sunpeng.li@....com>,
Christian König <christian.koenig@....com>,
"David (ChunMing) Zhou" <David1.Zhou@....com>,
David Airlie <airlied@...ux.ie>,
Bas Nieuwenhuizen <bas@...nieuwenhuizen.nl>,
Sean Paul <seanpaul@...omium.org>,
Sasha Levin <sashal@...nel.org>,
Mark Yacoub <markyacoub@...gle.com>,
Roman Li <Roman.Li@....com>,
Ikshwaku Chauhan <ikshwaku.chauhan@....corp-partner.google.com>,
Simon Ser <contact@...rsion.fr>, amd-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] BACKPORT: drm/amdgpu/disply: set num_crtc earlier
On Mon, May 30, 2022 at 05:29:02PM +0800, Ryan Lin wrote:
> From: Alex Deucher <alexander.deucher@....com>
>
> To avoid a recently added warning:
> Bogus possible_crtcs: [ENCODER:65:TMDS-65] possible_crtcs=0xf (full crtc mask=0x7)
> WARNING: CPU: 3 PID: 439 at drivers/gpu/drm/drm_mode_config.c:617 drm_mode_config_validate+0x178/0x200 [drm]
> In this case the warning is harmless, but confusing to users.
>
> Fixes: 0df108237433 ("drm: Validate encoder->possible_crtcs")
> Bug: https://bugzilla.kernel.org/show_bug.cgi?id=209123
> Reviewed-by: Daniel Vetter <daniel@...ll.ch>
> Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@....com>
> Signed-off-by: Alex Deucher <alexander.deucher@....com>
> Cc: stable@...r.kernel.org
Why did you not sign off on this?
And what is the git id of this in Linus's tree?
> Conflicts:
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> [Ryan Lin: Fixed the conflict, remove the non-main changed part
> of this patch]
No need for this here, right?
thanks,
greg k-h
Powered by blists - more mailing lists