Setting members to 0/NULL after a zalloc or calloc is redundant
authorBryce Harrington <bryce@osg.samsung.com>
Fri, 21 Nov 2014 06:21:56 +0000 (22:21 -0800)
committerPekka Paalanen <pekka.paalanen@collabora.co.uk>
Fri, 28 Nov 2014 14:10:04 +0000 (16:10 +0200)
commitbff3472e2eb2099e8d9e6e54af73030f25372fb7
tree51eee6c6298067c07b38330d5863c03e27919a04
parentde44761a1a51a7fb79f7d239b802fd3f1660f744
Setting members to 0/NULL after a zalloc or calloc is redundant

calloc (and zalloc) set the allocated memory to 0, so there's really no
need to do it manually.

Signed-off-by: Bryce Harrington <bryce@osg.samsung.com>
Reviewed-by: Marek Chalupa <mchqwerty@gmail.com>
[Pekka: dropped the src/evdev.c hunk.]
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
src/compositor-fbdev.c
src/compositor.c
src/gl-renderer.c
src/rpi-renderer.c