On Thu, Mar 23, 2017 at 1:22 PM, Colin King wrote:
> From: Colin Ian King
>
> info is being checked to see if it is a null pointer, however, vpgu is
> dereferencing info before this check, leading to a potential null
> pointer dereference. If info is null, then the error message being
> printed
On Thu, May 28, 2015 at 4:10 PM, Frediano Ziglio wrote:
>
>> also indicating in each patch what is a right now fix and what isn't.
>
> What do you mean by right fix or not ?
He probably meant indicating whether it is an urgent fix.
Frans
On Fri, Oct 31, 2014 at 11:34:45AM +0100, Roy Spliet wrote:
>
> It does ring a tiny bell: please check out
> https://bugs.freedesktop.org/show_bug.cgi?id=85160 and try the fix proposed
> in comment #7.
Yup, that seems to fix things. As far as I'm concerned, that patch is
Hi there,
My dual monitor setup on the Dell Precision M4500 is broken by commit
1dce6264045cd23e9c07574ed0bb31c7dce9354f ("drm/nv50/kms: Set VBLANK time
in modeset script"). I am no longer able to have more than one monitor
active.
Full dmesg can be found at http://pastebin.com/7e68yMRy, but I've
On Mon, Jun 1, 2015 at 11:08 AM, Christian König
wrote:
> Yeah, completely agree with Linus on the visibility problem and that's
> exactly the reason why we don't include in the kernel header and
> expect userspace to define the ISO types somewhere.
>
> But using the types from "include/linux/ty
