From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Matt Ranostay <matt.ranostay@intel.com>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: imu: mpu6050: fix possible NULL dereferences
Date: Sat, 5 Mar 2016 20:49:07 +0300 [thread overview]
Message-ID: <20160305174907.GY5273@mwanda> (raw)
In-Reply-To: <56DB1AF8.6010907@kernel.org>
On Sat, Mar 05, 2016 at 05:44:24PM +0000, Jonathan Cameron wrote:
> On 03/03/16 03:18, Matt Ranostay wrote:
> > Fix possible null dereferencing of i2c and spi driver data.
> Is there actually a way of making this happen? Far as I know
> both i2c and spi should always provide an appropriate value...
> Is it the absence of a dt match table that is causing the issue?
>
The original issue was a static checker warning of inconsistent NULL
checks. I don't know if it can actually be NULL.
regards,
dan carpenter
next prev parent reply other threads:[~2016-03-05 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 3:18 [PATCH] iio: imu: mpu6050: fix possible NULL dereferences Matt Ranostay
2016-03-05 17:44 ` Jonathan Cameron
2016-03-05 17:49 ` Dan Carpenter [this message]
2016-03-05 17:51 ` Jonathan Cameron
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=20160305174907.GY5273@mwanda \
--to=dan.carpenter@oracle.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=matt.ranostay@intel.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 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).