From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c-mxs: fix compile warning in mxs_i2c_xfer()
Date: Thu, 24 Nov 2011 09:29:03 +0100 [thread overview]
Message-ID: <20111124082903.GV19986@pengutronix.de> (raw)
In-Reply-To: <1322121140-5216-1-git-send-email-shawn.guo@linaro.org>
Hello Shawn,
On Thu, Nov 24, 2011 at 03:52:20PM +0800, Shawn Guo wrote:
> CC drivers/i2c/busses/i2c-mxs.o
> drivers/i2c/busses/i2c-mxs.c: In function ?mxs_i2c_xfer?:
> drivers/i2c/busses/i2c-mxs.c:196:6: warning: ?data? may be used uninitialized in this function
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
> drivers/i2c/busses/i2c-mxs.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-mxs.c b/drivers/i2c/busses/i2c-mxs.c
> index 7e78f7c..00f098f 100644
> --- a/drivers/i2c/busses/i2c-mxs.c
> +++ b/drivers/i2c/busses/i2c-mxs.c
> @@ -193,7 +193,7 @@ static int mxs_i2c_wait_for_data(struct mxs_i2c_dev *i2c)
>
> static int mxs_i2c_finish_read(struct mxs_i2c_dev *i2c, u8 *buf, int len)
> {
> - u32 data;
> + u32 data = 0;
> int i;
>
> for (i = 0; i < len; i++) {
Looks like a stupid compiler. Then better use
u32 uninitialized_var(data);
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-11-24 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 7:52 [PATCH] i2c-mxs: fix compile warning in mxs_i2c_xfer() Shawn Guo
2011-11-24 8:00 ` Wolfram Sang
2011-11-24 8:24 ` Shawn Guo
2011-11-24 8:29 ` Uwe Kleine-König [this message]
2011-11-24 8:37 ` Wolfram Sang
2011-11-24 9:02 ` Dong Aisheng-B29396
2011-11-24 9:06 ` Uwe Kleine-König
2011-11-24 9:09 ` Dong Aisheng-B29396
2011-11-24 9:11 ` Lothar Waßmann
2011-11-25 1:15 ` Shawn Guo
2011-11-25 9:08 ` Wolfram Sang
2011-12-02 19:42 ` Marek Vasut
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=20111124082903.GV19986@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).