From: Qianfeng Rong <rongqianfeng@vivo.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Jacopo Mondi <jacopo@jmondi.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"open list:MT9V111 APTINA CAMERA SENSOR"
<linux-media@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] media: i2c: mt9v111: fix incorrect type for ret
Date: Wed, 27 Aug 2025 23:41:26 +0800 [thread overview]
Message-ID: <411e9db5-5339-4527-bb3d-473b339a6572@vivo.com> (raw)
In-Reply-To: <xbmwlnflzhfhapyt5dinqqsdurxgu5imlqixudopb7z32eteth@cs7hulza54e3>
在 2025/8/27 20:58, Jacopo Mondi 写道:
> [You don't often get email from jacopo.mondi@ideasonboard.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi Qianfeng
>
> On Wed, Aug 27, 2025 at 08:39:10PM +0800, Qianfeng Rong wrote:
>> Change "ret" from unsigned int to int type in mt9v111_calc_frame_rate()
>> to store negative error codes or zero returned by __mt9v111_hw_reset()
>> and other functions.
>>
>> Storing the negative error codes in unsigned type, doesn't cause an issue
>> at runtime but it's ugly as pants.
>>
>> No effect on runtime.
> well, I'm not sure that's true.
>
> The code goes as
>
> ret = __mt9v111_hw_reset(mt9v111);
> if (ret == -EINVAL)
> ret = __mt9v111_sw_reset(mt9v111);
> if (ret)
> return ret;
>
> And if ret is unsigned the condition ret == -EINVAL will never be met.
>
> I guess this actually fixes a bug, doesn't it ?
> You can add:
>
> Cc: stable@vger.kernel.org
> Fixes: aab7ed1c3927 ("media: i2c: Add driver for Aptina MT9V111")
> Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
>
> Thanks
> j
I have written a test program on the arm64 platform:
unsigned int ret = -ENOMEM;
if (ret == -ENOMEM)
pr_info("unsigned int ret(%u) == -ENOMEM\n", ret);
else
pr_info("unsigned int ret(%u) != -ENOMEM\n", ret);
Output log is: unsigned int ret(4294967284) == -ENOMEM
I suspect that -ENOMEM is forcibly converted to an unsigned type during the
comparison, but I am not sure if this behavior is consistent across all
platforms and compilers. Therefore, I agree that your suggestion and will
submit the v2 version.
Best regards,
Qianfeng
next prev parent reply other threads:[~2025-08-27 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 12:39 [PATCH 0/5] media: use int type to store negative error codes Qianfeng Rong
2025-08-27 12:39 ` [PATCH 1/5] media: dvb: Use " Qianfeng Rong
2025-08-27 12:39 ` [PATCH 2/5] media: i2c: mt9v111: fix incorrect type for ret Qianfeng Rong
2025-08-27 12:58 ` Jacopo Mondi
2025-08-27 15:41 ` Qianfeng Rong [this message]
2025-08-27 16:24 ` Jacopo Mondi
2025-08-28 2:08 ` Qianfeng Rong
2025-08-28 6:40 ` Jacopo Mondi
2025-08-28 6:43 ` Sakari Ailus
2025-08-28 6:45 ` Sakari Ailus
2025-08-27 12:39 ` [PATCH 3/5] media: raspberrypi: use int type to store negative error codes Qianfeng Rong
2025-08-27 12:39 ` [PATCH 4/5] media: stm32-dcmi: " Qianfeng Rong
2025-08-27 12:39 ` [PATCH 5/5] media: redrat3: " Qianfeng Rong
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=411e9db5-5339-4527-bb3d-473b339a6572@vivo.com \
--to=rongqianfeng@vivo.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=jacopo@jmondi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox