From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, ribalda@chromium.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y] media: uvcvideo: Remove dangling pointers
Date: Fri, 28 Feb 2025 23:20:44 -0500 [thread overview]
Message-ID: <20250228185437-e7697605e8039f73@stable.kernel.org> (raw)
In-Reply-To: <20250228083505.2713073-1-ribalda@chromium.org>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
❌ Build failures detected
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: 221cd51efe4565501a3dbf04cc011b537dcce7fb
Status in newer kernel trees:
6.13.y | Present (different SHA1: 9edc7d25f7e4)
6.12.y | Present (different SHA1: 438bda062b2c)
6.6.y | Present (different SHA1: 4dbaa738c583)
6.1.y | Present (different SHA1: ccc601afaf47)
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly.
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y | Failed | N/A |
Build Errors:
Patch failed to apply on stable/linux-5.4.y. Reject:
diff a/drivers/media/usb/uvc/uvc_ctrl.c b/drivers/media/usb/uvc/uvc_ctrl.c (rejected hunks)
@@ -1577,7 +1612,7 @@ static int uvc_ctrl_commit_entity(struct uvc_device *dev,
if (!rollback && handle &&
ctrl->info.flags & UVC_CTRL_FLAG_ASYNCHRONOUS)
- ctrl->handle = handle;
+ uvc_ctrl_set_handle(handle, ctrl, handle);
}
return 0;
next prev parent reply other threads:[~2025-03-01 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 15:12 FAILED: patch "[PATCH] media: uvcvideo: Remove dangling pointers" failed to apply to 5.4-stable tree gregkh
2025-02-28 8:35 ` [PATCH 5.4.y] media: uvcvideo: Remove dangling pointers Ricardo Ribalda
2025-03-01 4:20 ` Sasha Levin [this message]
2025-03-05 10:30 ` Ricardo Ribalda
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=20250228185437-e7697605e8039f73@stable.kernel.org \
--to=sashal@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;
as well as URLs for NNTP newsgroup(s).