[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1jpj0ZCs81YJu0Dx3QFSypQ+VBr348UfEaagcuvM_1gA@mail.gmail.com>
Date: Tue, 6 Mar 2018 22:33:46 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Mike Snitzer <snitzer@...hat.com>
Cc: Alasdair Kergon <agk@...hat.com>, dm-devel@...hat.com,
Mikulas Patocka <mpatocka@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
Aliaksei Karaliou <akaraliou.dev@...il.com>,
Jens Axboe <axboe@...nel.dk>, Jan Kara <jack@...e.cz>,
Dan Carpenter <dan.carpenter@...cle.com>,
Mark Rutland <mark.rutland@....com>,
Eric Biggers <ebiggers@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>
Subject: Re: dm-bufio: avoid false-positive Wmaybe-uninitialized warning
On Thu, Feb 22, 2018 at 5:04 PM, Mike Snitzer <snitzer@...hat.com> wrote:
> On Thu, Feb 22 2018 at 10:56am -0500,
> Arnd Bergmann <arnd@...db.de> wrote:
>
> Mikulas already sent a fix for this:
> https://patchwork.kernel.org/patch/10211631/
>
> But I like yours a bit better, though I'll likely move the declaration
> of 'noio_flag' temporary inside the conditional.
>
> Anyway, I'll get this fixed up shortly, thanks.
I see the fix made it into linux-next on the same day, but the build bots still
report the warning for mainline kernels and now also for stable kernels
that got a backport of the patch that introduced it on arm64.
I assume you had not planned to send it for mainline, any chance you
could change that and send it as a bugfix with a 'Cc:
stable@...r.kernel.org' tag to restore a clean build?
Arnd
Powered by blists - more mailing lists