On Thu, May 31, 2012 at 11:31:50AM +0100, Chris Wilson wrote:
> On Thu, 31 May 2012 12:03:53 +0200, Daniel Vetter wrote:
> > On Thu, May 31, 2012 at 10:49:59AM +0100, Chris Wilson wrote:
> > > On Wed, 30 May 2012 15:34:20 +0200, Daniel Vetter
> > > wrote:
> > > > Instead of abusing into mode->cl
On Thu, 31 May 2012 12:03:53 +0200, Daniel Vetter wrote:
> On Thu, May 31, 2012 at 10:49:59AM +0100, Chris Wilson wrote:
> > On Wed, 30 May 2012 15:34:20 +0200, Daniel Vetter
> > wrote:
> > > Instead of abusing into mode->clock, because we should touch that
> > > one at all. First prep step to c
On Thu, May 31, 2012 at 10:49:59AM +0100, Chris Wilson wrote:
> On Wed, 30 May 2012 15:34:20 +0200, Daniel Vetter
> wrote:
> > Instead of abusing into mode->clock, because we should touch that
> > one at all. First prep step to constify the mode argument to the
> > intel_dp_mode_fixup function.
>
On Wed, 30 May 2012 15:34:20 +0200, Daniel Vetter
wrote:
> Instead of abusing into mode->clock, because we should touch that
> one at all. First prep step to constify the mode argument to the
> intel_dp_mode_fixup function.
>
> The next patch will stop us from modifying mode->clock.
>
> Signed-
Instead of abusing into mode->clock, because we should touch that
one at all. First prep step to constify the mode argument to the
intel_dp_mode_fixup function.
The next patch will stop us from modifying mode->clock.
Signed-Off-by: Daniel Vetter
---
drivers/gpu/drm/i915/intel_display.c | 16 +