mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
To: XiaxiShen <shenxiaxi26@gmail.com>,
	laurent.pinchart@ideasonboard.com, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pr_info("I changed uvcvideo driver in the Linux Kernel\n");
Date: Mon, 9 Jan 2023 17:13:57 +0100	[thread overview]
Message-ID: <49d1dece-cb90-23f3-977e-98905b1a0abc@collabora.com> (raw)
In-Reply-To: <20221230034634.7809-1-shenxiaxi26@gmail.com>

Hello XiaxiShen,

 From Documentation/process/researcher-guidelines.rst:

"The Linux kernel community expects that everyone interacting with the
project is participating in good faith to make Linux better."

Please explain how your patch will make Linux better. "I added a pr_info()
which emits information unrelated to work of the driver" is not enough of an
explanation.

Failing to do so and to adhere to the expectation quoted above
you risk any patches to the kernel submitted by you being disregarded.

Andrzej

W dniu 30.12.2022 o 04:46, XiaxiShen pisze:
> Signed-off-by: XiaxiShen <shenxiaxi26@gmail.com>
> ---
>   drivers/media/usb/uvc/uvc_driver.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c
> index e4bcb5011360..60778a5a2b4e 100644
> --- a/drivers/media/usb/uvc/uvc_driver.c
> +++ b/drivers/media/usb/uvc/uvc_driver.c
> @@ -2082,6 +2082,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");
> +
>   
>   	/* Allocate memory for the device and initialize it. */
>   	dev = kzalloc(sizeof(*dev), GFP_KERNEL);


  reply	other threads:[~2023-01-09 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  3:46 XiaxiShen
2023-01-09 16:13 ` Andrzej Pietrasiewicz [this message]
     [not found]   ` <CABtBSabksqweaDjhSVEaETYtCoQCVE1stPN7wwJr=eLPEU3X2w@mail.gmail.com>
2023-01-10 17:01     ` Andrzej Pietrasiewicz

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=49d1dece-cb90-23f3-977e-98905b1a0abc@collabora.com \
    --to=andrzej.p@collabora.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=shenxiaxi26@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

all inboxes | Powered by JetHome®