[PATCH] drmPrime*: initialize output args to 0

2015-05-05 Thread Guillaume Desmottes
On Tue, 2015-05-05 at 16:12 +0100, Emil Velikov wrote: > As mentioned before one could add the appropriate Valgrind > annotations. Although using memclear() or this will do just fine :-) > Any objections against memclear ? it will save us some head-scratching > when/if someone decides to extend str

[PATCH] drmPrime*: initialize output args to 0

2015-05-05 Thread Emil Velikov
Hi Guillaume, On 29 April 2015 at 09:16, Guillaume Desmottes wrote: > Fix Valgrind errors because those memory was uninitialized. > > https://bugs.freedesktop.org/show_bug.cgi?id=90194 > Signed-off-by: Guillaume Desmottes > --- > xf86drm.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --gi

[PATCH] drmPrime*: initialize output args to 0

2015-04-29 Thread Guillaume Desmottes
Fix Valgrind errors because those memory was uninitialized. https://bugs.freedesktop.org/show_bug.cgi?id=90194 Signed-off-by: Guillaume Desmottes --- xf86drm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/xf86drm.c b/xf86drm.c index f7c45f8..01c398e 100644 --- a/xf86drm.c +++ b/xf86drm.

[PATCH] drmPrime*: initialize output args to 0

2015-04-28 Thread Guillaume Desmottes
Fix Valgrind errors because those memory was uninitialized. https://bugs.freedesktop.org/show_bug.cgi?id=90194 Signed-off-by: Guillaume Desmottes --- xf86drm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/xf86drm.c b/xf86drm.c index f7c45f8..f3f84df 100644 --- a/xf86drm.c +++ b/xf86drm.