From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Shuah Khan <skhan@linuxfoundation.org>
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 17:13:11 +0100 [thread overview]
Message-ID: <20260220161311.GF1619026@killaraus.ideasonboard.com> (raw)
In-Reply-To: <4cb7125d-8023-4719-96e0-8322e4c6a241@linuxfoundation.org>
On Fri, Feb 20, 2026 at 08:49:47AM -0700, Shuah Khan wrote:
> 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
Thank you.
Jayesh, I assume this conversation took you by surprise, so I'll provide
a bit of context. LFD103 used to provide instructions on how to modify a
driver, create a patch and send it to a mailing list. Those instructions
were then followed by a line to tell the reader to not actually run the
commands. Unsurprisingly, that line was often overlooked, and patches
such as this one spammed the list.
I got a bit fed up and reported the issue to Shuah, who ensured LFD103
would be improved to avoid the problem. That was months ago, so I'm
surprised to see the issue occurring again. If you've followed the old
LFD103, I'm blaming the original wording of the course, not you, for the
problem.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2026-02-20 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 13:18 [PATCH] Modified uvc_driver 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
2026-02-20 16:13 ` Laurent Pinchart [this message]
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=20260220161311.GF1619026@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=jayeshkpuri@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.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