From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Vishal Parmar <vishistriker@gmail.com>,
laurent.pinchart@ideasonboard.com, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] first patch test
Date: Sat, 18 Feb 2023 16:41:27 +0700 [thread overview]
Message-ID: <Y/CdR0oBttYV85Y8@debian.me> (raw)
In-Reply-To: <20230218031238.5747-1-vishistriker@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
On Sat, Feb 18, 2023 at 08:42:37AM +0530, Vishal Parmar wrote:
> Signed-off-by: Vishal Parmar <vishistriker@gmail.com>
> ---
> drivers/media/usb/uvc/uvc_driver.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c
> index e4bcb5011360..c79dcee2213f 100644
> --- a/drivers/media/usb/uvc/uvc_driver.c
> +++ b/drivers/media/usb/uvc/uvc_driver.c
> @@ -2082,7 +2082,7 @@ 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");
> /* Allocate memory for the device and initialize it. */
> dev = kzalloc(sizeof(*dev), GFP_KERNEL);
> if (dev == NULL)
Hi and welcome to LKML!
As others has pointed, it seems like you had sent a patch which only
added noises to the ML. Also, I see that you send the similar change as
one in "Modifying a driver under the VM" section of kernelnewbies.org
[1].
If you'd like to submit patches, you can do so by contributing to
drivers/staging/ drivers first or documentation files at Documentation/.
It is not recommended to go outside of there until you've gained
experience and have several of your patches accepted and applied by
respective maintainers.
In any case, please read Documentation/process/submitting-patches.rst.
Thanks.
[1]: https://kernelnewbies.org/FirstKernelPatch
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-02-18 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 3:12 [PATCH] first patch test Vishal Parmar
2023-02-18 8:40 ` Sebastian Fricke
2023-02-18 9:41 ` Bagas Sanjaya [this message]
2023-02-18 12:52 ` 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=Y/CdR0oBttYV85Y8@debian.me \
--to=bagasdotme@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=vishistriker@gmail.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