Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1379283
| From | Dan Carpenter <dan.carpenter@oracle.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [patch] firmware: qemu_fw_cfg.c: potential unintialized variable |
| Date | 2016-04-14 22:10 +0200 |
| Message-ID | <rnVKp-7KX-9@gated-at.bofh.it> (permalink) |
| References | <rnLUL-83r-43@gated-at.bofh.it> <rnUv0-6rs-27@gated-at.bofh.it> <rnUY1-71M-7@gated-at.bofh.it> <rnVho-7bz-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Ah... I see now. You're right. Thanks for the explanation. On my config those functions are no-ops so the variable isn't initialized. If they were enabled then *probably* it wouldn't generate a warning. Probably just silencing the warning is the way to go though... I bet GCC optimizes it away. Let me think about this some more... regards, dan carpenter
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[patch] firmware: qemu_fw_cfg.c: potential unintialized variable Dan Carpenter <dan.carpenter@oracle.com> - 2016-04-14 11:40 +0200
Re: [patch] firmware: qemu_fw_cfg.c: potential unintialized variable "Gabriel L. Somlo" <somlo@cmu.edu> - 2016-04-14 20:50 +0200
Re: [patch] firmware: qemu_fw_cfg.c: potential unintialized variable Dan Carpenter <dan.carpenter@oracle.com> - 2016-04-14 21:20 +0200
Re: [patch] firmware: qemu_fw_cfg.c: potential unintialized variable "Gabriel L. Somlo" <somlo@cmu.edu> - 2016-04-14 21:40 +0200
Re: [patch] firmware: qemu_fw_cfg.c: potential unintialized variable Dan Carpenter <dan.carpenter@oracle.com> - 2016-04-14 22:10 +0200
Re: [patch] firmware: qemu_fw_cfg.c: potential unintialized variable "Gabriel L. Somlo" <somlo@cmu.edu> - 2016-04-14 22:00 +0200
csiph-web