From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Desnes Nunes <desnesn@redhat.com>,
hansg@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] media: uvcvideo: fix build error in uvc_ctrl_cleanup_fh
Date: Mon, 30 Jun 2025 18:29:52 +0300 [thread overview]
Message-ID: <20250630152952.GG24861@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCu83Ky-604gu2Yt34Wj1Km6Xh+TcPYzQxKZJNWdT7=m8A@mail.gmail.com>
On Mon, Jun 30, 2025 at 05:15:38PM +0200, Ricardo Ribalda wrote:
> Hi Desdes
>
> How did you trigger this build warning? I believe we use C11
>
> https://www.kernel.org/doc/html/latest/process/programming-language.html
Note that the local declaration of the loop counter shadows the global
one. I would have expected a different compiler warning though.
The shadowing was introduced by
commit 10acb9101355484c3e4f2625003cd1b6c203cfe4
Author: Ricardo Ribalda <ribalda@chromium.org>
Date: Thu Mar 27 21:05:29 2025 +0000
media: uvcvideo: Increase/decrease the PM counter per IOCTL
and I think it should be fixed (while at it, with an unsigned int local
loop counter instead of a signed int) as it's not a good practice.
> On Mon, 30 Jun 2025 at 17:07, Desnes Nunes <desnesn@redhat.com> wrote:
> >
> > This fixes the following compilation failure: "error: ‘for’ loop
> > initial declarations are only allowed in C99 or C11 mode"
> >
> > Cc: stable@vger.kernel.org
> > Fixes: 221cd51efe45 ("media: uvcvideo: Remove dangling pointers")
> > Signed-off-by: Desnes Nunes <desnesn@redhat.com>
> > ---
> > drivers/media/usb/uvc/uvc_ctrl.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/media/usb/uvc/uvc_ctrl.c b/drivers/media/usb/uvc/uvc_ctrl.c
> > index 44b6513c5264..532615d8484b 100644
> > --- a/drivers/media/usb/uvc/uvc_ctrl.c
> > +++ b/drivers/media/usb/uvc/uvc_ctrl.c
> > @@ -3260,7 +3260,7 @@ int uvc_ctrl_init_device(struct uvc_device *dev)
> > void uvc_ctrl_cleanup_fh(struct uvc_fh *handle)
> > {
> > struct uvc_entity *entity;
> > - int i;
> > + unsigned int i;
> >
> > guard(mutex)(&handle->chain->ctrl_mutex);
> >
> > @@ -3268,7 +3268,7 @@ void uvc_ctrl_cleanup_fh(struct uvc_fh *handle)
> > return;
> >
> > list_for_each_entry(entity, &handle->chain->dev->entities, list) {
> > - for (unsigned int i = 0; i < entity->ncontrols; ++i) {
> > + for (i = 0; i < entity->ncontrols; ++i) {
> > if (entity->controls[i].handle != handle)
> > continue;
> > uvc_ctrl_set_handle(handle, &entity->controls[i], NULL);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-06-30 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 15:01 [PATCH] media: uvcvideo: fix build error in uvc_ctrl_cleanup_fh Desnes Nunes
2025-06-30 15:15 ` Ricardo Ribalda
2025-06-30 15:29 ` Laurent Pinchart [this message]
2025-06-30 19:36 ` Desnes Nunes
2025-06-30 19:33 ` Desnes Nunes
2025-06-30 15:33 ` Greg KH
2025-06-30 19:38 ` Desnes Nunes
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=20250630152952.GG24861@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=desnesn@redhat.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=stable@vger.kernel.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