Re: linux-next: build failure after merge of the mmc tree
From: Ulf Hansson
Date: Mon Apr 26 2021 - 05:47:11 EST
On Mon, 26 Apr 2021 at 03:32, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
>
> Hi all,
>
> On Fri, 16 Apr 2021 13:49:07 +1000 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> >
> > This is actually just a warning.
> >
> > On Fri, 16 Apr 2021 13:48:27 +1000 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> > >
> > > After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
> > > failed like this:
> > >
> > > In file included from drivers/memstick/host/r592.h:13,
> > > from drivers/memstick/host/r592.c:21:
> > > drivers/memstick/host/r592.c: In function 'r592_flush_fifo_write':
> > > include/linux/kfifo.h:588:1: warning: ignoring return value of '__kfifo_uint_must_check_helper' declared with attribute 'warn_unused_result' [-Wunused-result]
> > > 588 | __kfifo_uint_must_check_helper( \
> > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 589 | ({ \
> > > | ~~~~
> > > 590 | typeof((fifo) + 1) __tmp = (fifo); \
> > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 591 | typeof(__tmp->ptr) __buf = (buf); \
> > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 592 | unsigned long __n = (n); \
> > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 593 | const size_t __recsize = sizeof(*__tmp->rectype); \
> > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 594 | struct __kfifo *__kfifo = &__tmp->kfifo; \
> > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 595 | (__recsize) ?\
> > > | ~~~~~~~~~~~~~~
> > > 596 | __kfifo_out_r(__kfifo, __buf, __n, __recsize) : \
> > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 597 | __kfifo_out(__kfifo, __buf, __n); \
> > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 598 | }) \
> > > | ~~~~
> > > 599 | )
> > > | ~
> > > drivers/memstick/host/r592.c:367:2: note: in expansion of macro 'kfifo_out'
> > > 367 | kfifo_out(&dev->pio_fifo, buffer, 4);
> > > | ^~~~~~~~~
> > >
> > > Caused by commit
> > >
> > > 4b00ed3c5072 ("memstick: r592: remove unused variable")
>
> I am still getting this warning ...
Apologize for the delay, it should be fixed now.
Kind regards
Uffe