From: Lars-Peter Clausen <lars@metafoo.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [staging:staging-next 84/99] drivers/staging/iio/adc/max1363_ring.c:87:7: warning: 'rxbuf' may b
Date: Tue, 10 Jul 2012 07:21:12 +0000 [thread overview]
Message-ID: <4FFBD7E8.5030107@metafoo.de> (raw)
In-Reply-To: <20120710004049.GA7404@localhost>
On 07/10/2012 02:40 AM, wfg@linux.intel.com wrote:
> Hi Lars-Peter,
>
> There are new compile warnings show up in
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-next
> head: f12db36d3fd7ab75c29015c32a12d49697e11f61
> commit: da0f01e1ed88b4ac650d884e4e2ee11c9cd4d83b [84/99] staging:iio:max1363: Do not return error code in interrupt handler
>
> All warnings:
>
> drivers/staging/iio/adc/max1363_ring.c: In function 'max1363_trigger_handler':
> drivers/staging/iio/adc/max1363_ring.c:87:7: warning: 'rxbuf' may be used uninitialized in this function [-Wmaybe-uninitialized]
>
Yea, known issue. I somehow managed to send out an outdated version of the
patch, the one I have locally does not have this issue. Will send out a fix
shortly.
Thanks for reporting.
- Lars
> vim +87 drivers/staging/iio/adc/max1363_ring.c
> 84
> 85 done:
> 86 iio_trigger_notify_done(indio_dev->trig);
> > 87 kfree(rxbuf);
> 88
> 89 return IRQ_HANDLED;
> 90 }
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Centre
> Fengguang Wu <wfg@linux.intel.com> Intel Corporation
prev parent reply other threads:[~2012-07-10 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 0:40 [staging:staging-next 84/99] drivers/staging/iio/adc/max1363_ring.c:87:7: warning: 'rxbuf' may be us wfg
2012-07-10 7:21 ` Lars-Peter Clausen [this message]
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=4FFBD7E8.5030107@metafoo.de \
--to=lars@metafoo.de \
--cc=kernel-janitors@vger.kernel.org \
/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