On Tue, 17 Nov 2015, John Harrison wrote:
> This seems to have caused a warning to appear. I generally build with
> -Werror which means my build is broken :(.
>
> intel_display.c: In function 'intel_user_framebuffer_create':
> i915/intel_display.c(14593)2: warning: passing argument 2 of
> 'intel
This seems to have caused a warning to appear. I generally build with
-Werror which means my build is broken :(.
intel_display.c: In function 'intel_user_framebuffer_create':
i915/intel_display.c(14593)2: warning: passing argument 2 of
'intel_framebuffer_create' discards 'const' qualifier from p
On Wed, Nov 11, 2015 at 07:11:29PM +0200, ville.syrjala at linux.intel.com
wrote:
> From: Ville Syrjälä
>
> Drivers shouldn't clobber the passed in addfb ioctl parameters.
> i915 was doing just that. To prevent it from happening again,
> pass the struct around as const, starting all the way fr
Hi,
On 11/11/15 17:11, ville.syrjala at linux.intel.com wrote:
> From: Ville Syrjälä
>
> Drivers shouldn't clobber the passed in addfb ioctl parameters.
> i915 was doing just that. To prevent it from happening again,
> pass the struct around as const, starting all the way from
> internal_frame
From: Ville Syrjälä
Drivers shouldn't clobber the passed in addfb ioctl parameters.
i915 was doing just that. To prevent it from happening again,
pass the struct around as const, starting all the way from
internal_framebuffer_create().
Signed-off-by: Ville Syrjälä
---
I tried to cross-compi
