From: Jens Axboe <axboe@kernel.dk>
To: ming.lei@redhat.com
Cc: lkp@intel.com, linux-block@vger.kernel.org
Subject: Re: [PATCH] ublk_drv: fix build warning with -Wmaybe-uninitialized and one sparse warning
Date: Sat, 16 Jul 2022 06:33:31 -0600 [thread overview]
Message-ID: <165797481124.363655.12942466690118689906.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220716095344.222674-1-ming.lei@redhat.com>
On Sat, 16 Jul 2022 17:53:44 +0800, Ming Lei wrote:
> After applying -Wmaybe-uninitialized manually, two build warnings are
> triggered:
>
> drivers/block/ublk_drv.c:940:11: warning: ‘io’ may be used uninitialized [-Wmaybe-uninitialized]
> 940 | io->flags &= ~UBLK_IO_FLAG_ACTIVE;
>
> drivers/block/ublk_drv.c: In function ‘ublk_ctrl_uring_cmd’:
> drivers/block/ublk_drv.c:1531:9: warning: ‘ret’ may be used uninitialized [-Wmaybe-uninitialized]
>
> [...]
Applied, thanks!
[1/1] ublk_drv: fix build warning with -Wmaybe-uninitialized and one sparse warning
commit: f2450f8a2c1ec3e88d6674f747b913aa5f21fa59
Best regards,
--
Jens Axboe
next prev parent reply other threads:[~2022-07-16 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 9:53 [PATCH] ublk_drv: fix build warning with -Wmaybe-uninitialized and one sparse warning Ming Lei
2022-07-16 12:33 ` Jens Axboe [this message]
2022-07-18 12:10 ` Ziyang Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165797481124.363655.12942466690118689906.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ming.lei@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox