| commit | 8cdb368d19e6568a3b17e9b5202a66cc0e2587d8 | |
| author | Marc-André Lureau <marcandre.lureau@redhat.com> | |
| Thu, 28 Mar 2024 10:20:50 +0000 (28 14:20 +0400) | ||
| committer | Philippe Mathieu-Daudé <philmd@linaro.org> | |
| Tue, 2 Apr 2024 14:15:07 +0000 (2 16:15 +0200) | ||
| tree | 59c2ad1afcfc7f0d2ad161deb50c12e679249d80 | treesnapshot (tar.gz zip) |
| parent | c65288de4de0552c15d6119098f0eaeb78ab4702 | commitdiff |
hw/nvme: fix -Werror=maybe-uninitialized
../hw/nvme/ctrl.c:6081:21: error: ‘result’ may be used uninitialized [-Werror=maybe-uninitialized]
It's not obvious that 'result' is set in all code paths. When &result is
a returned argument, it's even less clear.
Looking at various assignments, 0 seems to be a suitable default value.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
Message-ID: <20240328102052.3499331-18-marcandre.lureau@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
../hw/nvme/ctrl.c:6081:21: error: ‘result’ may be used uninitialized [-Werror=maybe-uninitialized]
It's not obvious that 'result' is set in all code paths. When &result is
a returned argument, it's even less clear.
Looking at various assignments, 0 seems to be a suitable default value.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
Message-ID: <20240328102052.3499331-18-marcandre.lureau@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
| hw/nvme/ctrl.c | diffblobblamehistory |