* Re: dm-bufio: avoid false-positive Wmaybe-uninitialized warning [not found] ` <20180222160432.GA16971@redhat.com> @ 2018-03-06 21:33 ` Arnd Bergmann 2018-03-07 1:29 ` Mike Snitzer 0 siblings, 1 reply; 3+ messages in thread From: Arnd Bergmann @ 2018-03-06 21:33 UTC (permalink / raw) To: Mike Snitzer Cc: Alasdair Kergon, dm-devel, Mikulas Patocka, Ingo Molnar, Aliaksei Karaliou, Jens Axboe, Jan Kara, Dan Carpenter, Mark Rutland, Eric Biggers, Linux Kernel Mailing List, stable On Thu, Feb 22, 2018 at 5:04 PM, Mike Snitzer <snitzer@redhat.com> wrote: > On Thu, Feb 22 2018 at 10:56am -0500, > Arnd Bergmann <arnd@arndb.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@vger.kernel.org' tag to restore a clean build? Arnd ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: dm-bufio: avoid false-positive Wmaybe-uninitialized warning 2018-03-06 21:33 ` dm-bufio: avoid false-positive Wmaybe-uninitialized warning Arnd Bergmann @ 2018-03-07 1:29 ` Mike Snitzer 2018-03-07 8:48 ` Arnd Bergmann 0 siblings, 1 reply; 3+ messages in thread From: Mike Snitzer @ 2018-03-07 1:29 UTC (permalink / raw) To: Arnd Bergmann Cc: Alasdair Kergon, dm-devel, Mikulas Patocka, Ingo Molnar, Aliaksei Karaliou, Jens Axboe, Jan Kara, Dan Carpenter, Mark Rutland, Eric Biggers, Linux Kernel Mailing List, stable On Tue, Mar 06 2018 at 4:33pm -0500, Arnd Bergmann <arnd@arndb.de> wrote: > On Thu, Feb 22, 2018 at 5:04 PM, Mike Snitzer <snitzer@redhat.com> wrote: > > On Thu, Feb 22 2018 at 10:56am -0500, > > Arnd Bergmann <arnd@arndb.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@vger.kernel.org' tag to restore a clean build? I did/do plan to send to Linus this week. But I've updated the commit header to include the CC: stable like you asked. Thanks, Mike ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: dm-bufio: avoid false-positive Wmaybe-uninitialized warning 2018-03-07 1:29 ` Mike Snitzer @ 2018-03-07 8:48 ` Arnd Bergmann 0 siblings, 0 replies; 3+ messages in thread From: Arnd Bergmann @ 2018-03-07 8:48 UTC (permalink / raw) To: Mike Snitzer Cc: Alasdair Kergon, dm-devel, Mikulas Patocka, Ingo Molnar, Aliaksei Karaliou, Jens Axboe, Jan Kara, Dan Carpenter, Mark Rutland, Eric Biggers, Linux Kernel Mailing List, stable On Wed, Mar 7, 2018 at 2:29 AM, Mike Snitzer <snitzer@redhat.com> wrote: > On Tue, Mar 06 2018 at 4:33pm -0500, > Arnd Bergmann <arnd@arndb.de> wrote: > >> On Thu, Feb 22, 2018 at 5:04 PM, Mike Snitzer <snitzer@redhat.com> wrote: >> > On Thu, Feb 22 2018 at 10:56am -0500, >> > Arnd Bergmann <arnd@arndb.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@vger.kernel.org' tag to restore a clean build? > > I did/do plan to send to Linus this week. > > But I've updated the commit header to include the CC: stable like you > asked. Got it, thanks a lot, that brings us down to two kernelci warnings for 4.16 and one for 4.15-stable then. Arnd ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-03-07 8:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20180222155627.1800948-1-arnd@arndb.de>
[not found] ` <20180222160432.GA16971@redhat.com>
2018-03-06 21:33 ` dm-bufio: avoid false-positive Wmaybe-uninitialized warning Arnd Bergmann
2018-03-07 1:29 ` Mike Snitzer
2018-03-07 8:48 ` Arnd Bergmann
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox