From: jacopo mondi <jacopo@jmondi.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 1/1] mt9v111: Fix compiler warning by initialising a variable
Date: Mon, 30 Jul 2018 09:51:25 +0200 [thread overview]
Message-ID: <20180730075125.GE7615@w540> (raw)
In-Reply-To: <20180730072627.32014-1-sakari.ailus@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
Hi Sakari,
On Mon, Jul 30, 2018 at 10:26:27AM +0300, Sakari Ailus wrote:
> While this isn't a bug, initialise the variable to quash the warning.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> drivers/media/i2c/mt9v111.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/i2c/mt9v111.c b/drivers/media/i2c/mt9v111.c
> index da8f6ab91307..58d5f2224bff 100644
> --- a/drivers/media/i2c/mt9v111.c
> +++ b/drivers/media/i2c/mt9v111.c
> @@ -884,7 +884,7 @@ static int mt9v111_set_format(struct v4l2_subdev *subdev,
> struct v4l2_mbus_framefmt new_fmt;
> struct v4l2_mbus_framefmt *__fmt;
> unsigned int best_fit = ~0L;
> - unsigned int idx;
> + unsigned int idx = 0;
> unsigned int i;
>
Thanks for this, but there is already a patch sent on Friday by Jasmin
addressing the warning
https://patchwork.kernel.org/patch/10547983/
> mutex_lock(&mt9v111->stream_mutex);
> --
> 2.11.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-07-30 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 7:26 [PATCH 1/1] mt9v111: Fix compiler warning by initialising a variable Sakari Ailus
2018-07-30 7:51 ` jacopo mondi [this message]
2018-07-30 8:04 ` Sakari Ailus
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=20180730075125.GE7615@w540 \
--to=jacopo@jmondi.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.