On 10/08/17 12:01 AM, Harry Wentland wrote: > From: Andrey Grodzovsky <Andrey.Grodzovsky at amd.com> > > Change-Id: I37d313ca0e17b0d446a68575cafa94165849024e > Signed-off-by: Charlene Liu <charlene.liu at amd.com> > Reviewed-by: Vitaly Prosyak <Vitaly.Prosyak at amd.com> > Acked-by: Harry Wentland <Harry.Wentland at amd.com> > --- > drivers/gpu/drm/amd/display/dc/calcs/dcn_calcs.c | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/drivers/gpu/drm/amd/display/dc/calcs/dcn_calcs.c b/drivers/gpu/drm/amd/display/dc/calcs/dcn_calcs.c > index 875b98dae6e1..be6e3ca9fb0d 100644 > --- a/drivers/gpu/drm/amd/display/dc/calcs/dcn_calcs.c > +++ b/drivers/gpu/drm/amd/display/dc/calcs/dcn_calcs.c > @@ -856,8 +856,6 @@ bool dcn_validate_bandwidth( > - pipe->stream->timing.v_front_porch; > v->vactive[input_idx] = pipe->stream->timing.v_addressable; > v->pixel_clock[input_idx] = pipe->stream->timing.pix_clk_khz / 1000.0f; > - if (pipe->stream->timing.pixel_encoding == PIXEL_ENCODING_YCBCR420) > - v->pixel_clock[input_idx] /= 2; This code change doesn't seem to correspond to the commit log? It looks like this reverts a previous patch in the series. There are other cases where a patch is reverted, and then possibly another patch has a revision of the same change. Would be it possible to eliminate that kind of redundancy before sending out a series like this? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
