From: Jonathan Cameron <jic23@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Jonathan Cameron <jic23@cam.ac.uk>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: inkern: fix iio_convert_raw_to_processed_unlocked
Date: Wed, 03 Jul 2013 20:42:59 +0100 [thread overview]
Message-ID: <51D47EC3.5080305@kernel.org> (raw)
In-Reply-To: <20130701152004.cfddc36e7b3d9d63e1960514@linux-foundation.org>
On 07/01/2013 11:20 PM, Andrew Morton wrote:
> On Mon, 1 Jul 2013 18:40:09 +0200 Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
>
>> When reading IIO_CHAN_INFO_OFFSET, the return value of iio_channel_read() for
>> success will be IIO_VAL*, checking for 0 is not correct.
>
> I have a canned response:
>
> When writing a changelog, please describe the end-user-visible effects
> of the bug, so that others can more easily decide which kernel
> version(s) should be fixed, and so that downstream kernel maintainers
> can more easily work out whether this patch will fix a problem which
> they or their customers are observing.
>
>> Cc: <stable@vger.kernel.org> # 3.10.x
>
> Especially when cc'ing -stable.
>
As Andrew suggested I have added a few more details and applied the patch
to the fixes-togreg branch of iio.git.
Thanks,
Jonathan
prev parent reply other threads:[~2013-07-03 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 16:40 [PATCH] iio: inkern: fix iio_convert_raw_to_processed_unlocked Alexandre Belloni
2013-07-01 22:20 ` Andrew Morton
2013-07-03 19:42 ` 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=51D47EC3.5080305@kernel.org \
--to=jic23@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
/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.