From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Andrew Morton" <akpm@linux-foundation.org>,
"Éric Piel" <eric.piel@tremplin-utc.net>,
"Ilkka Koskinen" <ilkka.koskinen@nokia.com>
Cc: linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
stable@kernel.org
Subject: [PATCH 1/2] lis3lv02d: Fix read() call in lis3lv02d_get_odr()
Date: Tue, 6 Sep 2011 00:12:28 -0700 [thread overview]
Message-ID: <1315293149-3881-1-git-send-email-broonie@opensource.wolfsonmicro.com> (raw)
The driver is passing a struct lis3lv02d ** to the read() operation but
the read() operation wants a struct lis3lv02d * causing compiler warnings
and presumably also runtime problems.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: stable@kernel.org
---
drivers/misc/lis3lv02d/lis3lv02d.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/misc/lis3lv02d/lis3lv02d.c b/drivers/misc/lis3lv02d/lis3lv02d.c
index e67dcea..72a1f92 100644
--- a/drivers/misc/lis3lv02d/lis3lv02d.c
+++ b/drivers/misc/lis3lv02d/lis3lv02d.c
@@ -200,7 +200,7 @@ static int lis3lv02d_get_odr(struct lis3lv02d *lis3)
u8 ctrl;
int shift;
- lis3->read(&lis3, CTRL_REG1, &ctrl);
+ lis3->read(lis3, CTRL_REG1, &ctrl);
ctrl &= lis3->odr_mask;
shift = ffs(lis3->odr_mask) - 1;
return lis3->odrs[(ctrl >> shift)];
--
1.7.5.4
next reply other threads:[~2011-09-06 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 7:12 Mark Brown [this message]
2011-09-06 7:12 ` [PATCH 2/2] lis3lv02d: Make regulator API usage unconditional Mark Brown
2011-09-06 21:07 ` [PATCH 1/2] lis3lv02d: Fix read() call in lis3lv02d_get_odr() Andrew Morton
2011-09-07 5:21 ` Mark Brown
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=1315293149-3881-1-git-send-email-broonie@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=ilkka.koskinen@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 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).