All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the device-mapper tree
Date: Tue, 19 Feb 2019 22:35:39 -0500	[thread overview]
Message-ID: <20190220033539.GA17586@redhat.com> (raw)
In-Reply-To: <20190220131555.15317a39@canb.auug.org.au>

On Tue, Feb 19 2019 at  9:15pm -0500,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> After merging the device-mapper tree, today's linux-next build
> (powerpc_ppc64_defconfig) produced this warning:
> 
> In file included from include/linux/blkdev.h:21,
>                  from include/linux/blk-mq.h:5,
>                  from drivers/md/dm-core.h:14,
>                  from drivers/md/dm.c:8:
> drivers/md/dm.c: In function 'dec_pending':
> include/linux/bio.h:626:15: warning: 'bio' may be used uninitialized in this function [-Wmaybe-uninitialized]
>   bio->bi_next = bl->head;
>   ~~~~~~~~~~~~~^~~~~~~~~~
> drivers/md/dm.c:930:14: note: 'bio' was declared here
>   struct bio *bio;
>               ^~~
> 
> Introduced by commit
> 
>   58c66b86cfe7 ("dm: improve noclone_endio() to support multipath target")

Thanks, I've fixed it up.

Mike

  reply	other threads:[~2019-02-20  3:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  2:15 linux-next: build warning after merge of the device-mapper tree Stephen Rothwell
2019-02-20  3:35 ` Mike Snitzer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-09  8:57 Stephen Rothwell
2024-07-09  9:56 ` Mikulas Patocka
2024-07-09 22:28   ` Stephen Rothwell
2024-07-10 15:48     ` Mikulas Patocka
2024-07-30 10:07       ` Stephen Rothwell
2024-07-30 11:54         ` Mikulas Patocka
2024-07-30 13:36           ` Stephen Rothwell
2024-02-08  3:42 Stephen Rothwell
2021-07-21  7:34 Stephen Rothwell
2021-08-10  9:31 ` Stephen Rothwell
2021-01-22  6:56 Stephen Rothwell
2020-07-09  3:26 Stephen Rothwell
2020-07-09  4:38 ` yangerkun
2018-09-18  1:53 Stephen Rothwell
2017-12-11  2:05 Stephen Rothwell
2017-12-11  5:24 ` Mike Snitzer
2017-12-11  5:43   ` Stephen Rothwell

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=20190220033539.GA17586@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.