linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the gpio tree
Date: Thu, 16 Jun 2016 12:02:24 +0200	[thread overview]
Message-ID: <CACRpkdaJFO_PnXTFTsyCT4WxneRF7sYyu+1H5fKCr0ybYQB6OQ@mail.gmail.com> (raw)
In-Reply-To: <20160616143200.586e649d@canb.auug.org.au>

On Thu, Jun 16, 2016 at 6:32 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> After merging the gpio tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from drivers/gpio/gpiolib.c:25:0:
> drivers/gpio/gpiolib.c: In function 'lineevent_irq_thread':
> include/linux/kfifo.h:403:39: warning: 'ge.id' may be used uninitialized in this function [-Wmaybe-uninitialized]
>     )[__kfifo->in & __tmp->kfifo.mask] = \
>                                        ^
> drivers/gpio/gpiolib.c:657:24: note: 'ge.id' was declared here
>   struct gpioevent_data ge;
>                         ^
>
> Introduced by commit
>
>   61f922db7221 ("gpio: userspace ABI for reading GPIO line events")
>
> This is in the kfifo_put() call.

Thanks Stephen, Arnd has already helpfully made a patch to fix it :)

Yours,
Linus Walleij

  reply	other threads:[~2016-06-16 10:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16  4:32 linux-next: build warning after merge of the gpio tree Stephen Rothwell
2016-06-16 10:02 ` Linus Walleij [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-02  8:36 Stephen Rothwell
2020-01-09  4:16 Stephen Rothwell
2019-11-05  6:43 Stephen Rothwell
2019-11-07  8:35 ` Linus Walleij
2019-06-27  8:19 Stephen Rothwell
2019-06-27 14:57 ` Linus Walleij
2019-02-25  4:52 Stephen Rothwell
2018-12-18  5:41 Stephen Rothwell
2018-11-06  1:15 Stephen Rothwell
2018-11-06  7:24 ` Uwe Kleine-König
2018-01-11  4:06 Stephen Rothwell
2018-01-11  9:19 ` Linus Walleij
2017-05-30  3:52 Stephen Rothwell
2016-11-14  5:31 Stephen Rothwell
2016-09-13  3:18 Stephen Rothwell
2014-03-07  3:59 Stephen Rothwell
2014-03-07  6:16 ` Linus Walleij

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=CACRpkdaJFO_PnXTFTsyCT4WxneRF7sYyu+1H5fKCr0ybYQB6OQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).