From: Benjamin Mugnier <benjamin.mugnier@foss.st.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Sylvain Petinot <sylvain.petinot@foss.st.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
<linux-media@vger.kernel.org>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] media: i2c: st-vgxy61: remove redundant initialization of pointer mode
Date: Fri, 9 Feb 2024 09:55:40 +0100 [thread overview]
Message-ID: <c744b760-4bed-44cf-b079-eb21f3697425@foss.st.com> (raw)
In-Reply-To: <20240205220508.1851545-1-colin.i.king@gmail.com>
Hi Colin,
Thank you for your patch.
Reviewed-by: Benjamin Mugnier <benjamin.mugnier@foss.st.com>
On 2/5/24 23:05, Colin Ian King wrote:
> The pointer mode is being initialized with a value that is never
> read, it is being re-assigned later on. The initialization is
> redundant and can be removed.
>
> Cleans up clang scan build warning:
> drivers/media/i2c/st-vgxy61.c:632:33: warning: Value stored to 'mode'
> during its initialization is never read [deadcode.DeadStores]
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/media/i2c/st-vgxy61.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/i2c/st-vgxy61.c b/drivers/media/i2c/st-vgxy61.c
> index 2d64466d7ecf..b9e7c57027b1 100644
> --- a/drivers/media/i2c/st-vgxy61.c
> +++ b/drivers/media/i2c/st-vgxy61.c
> @@ -629,7 +629,7 @@ static int vgxy61_try_fmt_internal(struct v4l2_subdev *sd,
> const struct vgxy61_mode_info **new_mode)
> {
> struct vgxy61_dev *sensor = to_vgxy61_dev(sd);
> - const struct vgxy61_mode_info *mode = sensor->sensor_modes;
> + const struct vgxy61_mode_info *mode;
> unsigned int index;
>
> for (index = 0; index < ARRAY_SIZE(vgxy61_supported_codes); index++) {
--
Regards,
Benjamin
prev parent reply other threads:[~2024-02-09 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 22:05 Colin Ian King
2024-02-09 8:55 ` Benjamin Mugnier [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=c744b760-4bed-44cf-b079-eb21f3697425@foss.st.com \
--to=benjamin.mugnier@foss.st.com \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sylvain.petinot@foss.st.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
all inboxes | Powered by JetHome®