From: Lars-Peter Clausen <lars@metafoo.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [staging:staging-next 86/99] drivers/staging/iio/adc/ad7298_ring.c:97:37: warning: 'time_ns' may
Date: Fri, 13 Jul 2012 06:49:24 +0000 [thread overview]
Message-ID: <4FFFC4F4.4050106@metafoo.de> (raw)
In-Reply-To: <20120713051049.GC15846@localhost>
On 07/13/2012 07:10 AM, Fengguang Wu wrote:
> Hi Lars-Peter,
>
> There are compile warnings in
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-next
> head: bd972ff3176caf91a49d1d754848c3f6c5435328
> commit: 3879089ba3421bc8136025837b1a532729643371 [86/99] staging:iio:max1363: Don't free uninitialized variable
>
> All warnings:
>
> drivers/staging/iio/adc/ad7298_ring.c:97:37: warning: 'time_ns' may be used uninitialized in this function [-Wmaybe-uninitialized]
>
Hi,
I don't think the warning is caused by that commit. The file in question is
not affected by it.
> vim +97 drivers/staging/iio/adc/ad7298_ring.c
> 94 indio_dev->masklength); i++)
> 95 buf[i] = be16_to_cpu(st->rx_buf[i]);
> 96
> > 97 indio_dev->buffer->access->store_to(ring, (u8 *)buf, time_ns);
> 98
> 99 done:
> 100 iio_trigger_notify_done(indio_dev->trig);
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Centre
> Fengguang Wu <wfg@linux.intel.com> Intel Corporation
next prev parent reply other threads:[~2012-07-13 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 5:10 [staging:staging-next 86/99] drivers/staging/iio/adc/ad7298_ring.c:97:37: warning: 'time_ns' may be Fengguang Wu
2012-07-13 6:49 ` Lars-Peter Clausen [this message]
2012-07-13 7:06 ` [staging:staging-next 86/99] drivers/staging/iio/adc/ad7298_ring.c:97:37: warning: 'time_ns' may Fengguang Wu
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=4FFFC4F4.4050106@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.