All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Michael Hennerich <michael.hennerich@analog.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>,
	"fengguang.wu@intel.com" <fengguang.wu@intel.com>
Subject: Re: [PATCH] iio: staging: ad7298_ring: Fix maybe-uninitialized warning
Date: Mon, 16 Jul 2012 12:27:35 +0100	[thread overview]
Message-ID: <5003FAA7.4070602@cam.ac.uk> (raw)
In-Reply-To: <alpine.DEB.2.01.1207161155350.18056@pmeerw.net>

On 7/16/2012 11:02 AM, Peter Meerwald wrote:
>
>> Well - calling a function to initialize a variable which isn't being used
>> anywhere doesn't make more sense.
>
>> IMHO a more adequate fix would be to remove the timestamp argument from
>> store_to(),
>> since it isn't used anywhere.
>
> so
> indio_dev->buffer->access->store_to(ring, (u8 *)buf, time_ns);
> should become
> iio_push_to_buffer(buffer, (u8 *)data->buffer, time_ns);
> and you suggest to drop the last argument?
>
> I wasn't aware that timestamp is not used; at least iio_store_to_kfifo()
> and iio_store_to_sw_ring() just ignore it
>
Yes. Been meaning to clean that up for a while, but as one of the
multiple buffer patches removes all those calls anyway I'll
kill it whilst doing that.

      reply	other threads:[~2012-07-16 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16  8:42 [PATCH] iio: staging: ad7298_ring: Fix maybe-uninitialized warning michael.hennerich
2012-07-16  9:26 ` Peter Meerwald
2012-07-16  9:49   ` Michael Hennerich
2012-07-16 10:02     ` Peter Meerwald
2012-07-16 11:27       ` Jonathan Cameron [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=5003FAA7.4070602@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=fengguang.wu@intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=pmeerw@pmeerw.net \
    /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.