From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] media: i2c: ds90ub9x3: Fix use of uninitialized variables
Date: Thu, 3 Aug 2023 14:57:11 +0300 [thread overview]
Message-ID: <ZMuWF71x0thq/aTs@smile.fi.intel.com> (raw)
In-Reply-To: <20230803-ub9xx-uninit-vars-v1-1-284a5455260f@ideasonboard.com>
On Thu, Aug 03, 2023 at 11:41:38AM +0300, Tomi Valkeinen wrote:
> smatch reports some uninitialized variables:
>
> drivers/media/i2c/ds90ub913.c:481 ub913_log_status() error: uninitialized symbol 'v1'.
> drivers/media/i2c/ds90ub913.c:481 ub913_log_status() error: uninitialized symbol 'v2'.
> drivers/media/i2c/ds90ub953.c:655 ub953_log_status() error: uninitialized symbol 'gpio_local_data'.
> drivers/media/i2c/ds90ub953.c:655 ub953_log_status() error: uninitialized symbol 'gpio_input_ctrl'.
> drivers/media/i2c/ds90ub953.c:655 ub953_log_status() error: uninitialized symbol 'gpio_pin_sts'.
>
> These are used only for printing debug information, and the use of an
> uninitialized variable only happens if an i2c transaction has failed,
> which will print an error. Thus, fix the errors just by initializing the
> variables to 0.
>
> Fixes: 6363db1c9d45 ("media: i2c: add DS90UB953 driver")
> Fixes: c158d0d4ff15 ("media: i2c: add DS90UB913 driver")
I would prefer two separate changes on per driver basis. This is a good
practice to make backporting easier (generally speaking).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-08-03 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 8:41 [PATCH 0/2] media: i2c: ds90ubxxx: Fix uninitialized variable uses Tomi Valkeinen
2023-08-03 8:41 ` [PATCH 1/2] media: i2c: ds90ub9x3: Fix use of uninitialized variables Tomi Valkeinen
2023-08-03 11:57 ` Andy Shevchenko [this message]
2023-08-03 11:59 ` Tomi Valkeinen
2023-08-03 21:46 ` Laurent Pinchart
2023-08-04 5:49 ` Tomi Valkeinen
2023-08-04 9:00 ` Laurent Pinchart
2023-08-03 8:41 ` [PATCH 2/2] media: i2c: ds90ub960: Fix PLL config for 1200 MHz CSI rate Tomi Valkeinen
2023-08-03 21:43 ` Laurent Pinchart
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=ZMuWF71x0thq/aTs@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.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