From: Shuah Khan <skhan@linuxfoundation.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Jayesh Puri <jayeshkpuri@gmail.com>,
mchehab@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Modified uvc_driver
Date: Fri, 20 Feb 2026 08:49:47 -0700 [thread overview]
Message-ID: <4cb7125d-8023-4719-96e0-8322e4c6a241@linuxfoundation.org> (raw)
In-Reply-To: <20260220102749.GC1619026@killaraus.ideasonboard.com>
On 2/20/26 03:27, Laurent Pinchart wrote:
> On Thu, Feb 19, 2026 at 01:24:23PM -0700, Shuah Khan wrote:
>> On 2/19/26 06:32, Laurent Pinchart wrote:
>>> On Thu, Feb 19, 2026 at 06:48:11PM +0530, Jayesh Puri wrote:
>>>> ---
>>>> Kconfig | 0
>>>> drivers/media/usb/uvc/uvc_driver.c | 2 ++
>>>> 2 files changed, 2 insertions(+)
>>>> mode change 100644 => 100755 Kconfig
>>>>
>>>> diff --git a/Kconfig b/Kconfig
>>>> old mode 100644
>>>> new mode 100755
>>>> diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c
>>>> index aa3e8d295e0f..cec117328ab2 100644
>>>> --- a/drivers/media/usb/uvc/uvc_driver.c
>>>> +++ b/drivers/media/usb/uvc/uvc_driver.c
>>>> @@ -2191,6 +2191,8 @@ static int uvc_probe(struct usb_interface *intf,
>>>> (const struct uvc_device_info *)id->driver_info;
>>>> int function;
>>>> int ret;
>>>> +
>>>> + pr_info("I changed uvcvideo driver in the Linux Kernel\n");
>>>
>>> Congratulations, but I'm afraid we're out of medals.
>>>
>>> Shuah, I thought LFD103 has been updated to avoid spamming the lists
>>> with such patches. What happened ?
>>
>> It is changed a while back - not sure what's going on.
>
> Could you please investigate ?
>
I will look into it
thanks,
-- Shuah
next prev parent reply other threads:[~2026-02-20 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 13:18 Jayesh Puri
2026-02-19 13:32 ` Laurent Pinchart
2026-02-19 20:24 ` Shuah Khan
2026-02-20 10:27 ` Laurent Pinchart
2026-02-20 15:49 ` Shuah Khan [this message]
2026-02-20 16:13 ` Laurent Pinchart
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=4cb7125d-8023-4719-96e0-8322e4c6a241@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jayeshkpuri@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®