Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings
(e.g. "unused variable"). If the compiler thinks it is uninitialized,
either simply initialize the variable or make compiler changes.
As recommended[2] by[3] Linus[4], remove the macro. With the recent
change to disable -Wmaybe-uninitialized in v5.7 in commit
|
||
|---|---|---|
| .. | ||
| bug.h | ||
| compiler.h | ||
| device.h | ||
| dma-mapping.h | ||
| err.h | ||
| export.h | ||
| hrtimer.h | ||
| irqreturn.h | ||
| kernel.h | ||
| kmemleak.h | ||
| module.h | ||
| printk.h | ||
| ratelimit.h | ||
| scatterlist.h | ||
| slab.h | ||
| thread_info.h | ||
| uaccess.h | ||
| uio.h | ||
| virtio.h | ||
| virtio_byteorder.h | ||
| virtio_config.h | ||
| virtio_ring.h | ||
| vringh.h | ||