From: Jonathan Cameron <jic23@kernel.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: Re: [PATCH] iio: pressure: bmp280: Fix incorrect pointer access in PM callbacks
Date: Mon, 15 Aug 2016 15:46:44 +0100 [thread overview]
Message-ID: <beadcc22-db37-8f5b-9ce0-0d85e935013f@kernel.org> (raw)
In-Reply-To: <e2104071-78df-e83d-4dcf-fbb37ee36eed@linux.intel.com>
On 12/08/16 13:36, Jarkko Nikula wrote:
> On 08/12/2016 03:21 PM, Linus Walleij wrote:
>> On Fri, Aug 12, 2016 at 1:44 PM, Jarkko Nikula
>> <jarkko.nikula@linux.intel.com> wrote:
>>
>>> BMP280 runtime PM callbacks are incorrectly casting dev_get_drvdata() to
>>> struct bmp280_data * while bmp280_common_probe() sets driver data to
>>> struct iio_dev *. Fix this and get the struct bmp280_data * from private
>>> data of struct iio_dev.
>>>
>>> Fixes: 3d838118c6aa ("iio: pressure: bmp280: add power management")
>>> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>>> ---
>>> For v4.8-rc.
>>
>> Sent a fix for this already two weeks ago:
>> http://marc.info/?l=linux-iio&m=146965159217655&w=2
>>
>> Just waiting for it to be picked up and merged.
>>
> Ok, please feel free to add my tested by to your patch then
>
> Tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Added.
prev parent reply other threads:[~2016-08-15 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 11:44 [PATCH] iio: pressure: bmp280: Fix incorrect pointer access in PM callbacks Jarkko Nikula
2016-08-12 12:21 ` Linus Walleij
2016-08-12 12:36 ` Jarkko Nikula
2016-08-15 14:46 ` 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=beadcc22-db37-8f5b-9ce0-0d85e935013f@kernel.org \
--to=jic23@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--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 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).