On Sat, Sep 16, 2023 at 11:10:20PM +0530, Bragatheswaran Manickavel wrote:
> Fix some checkpatch complaints in usb/usbip/stub_dev.c
>
> Signed-off-by: Bragatheswaran Manickavel <bragathemanick0908@xxxxxxxxx>
> ---
> drivers/usb/usbip/stub_dev.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/usb/usbip/stub_dev.c b/drivers/usb/usbip/stub_dev.c
> index 9c6954aad6c8..3a5771f74a3f 100644
> --- a/drivers/usb/usbip/stub_dev.c
> +++ b/drivers/usb/usbip/stub_dev.c
> @@ -495,24 +495,25 @@ static void stub_disconnect(struct usb_device *udev)
> busid_priv->status = STUB_BUSID_ADDED;
> /* release busid_lock */
> spin_unlock(&busid_priv->busid_lock);
> - return;
> }
>
> #ifdef CONFIG_PM
>
> -/* These functions need usb_port_suspend and usb_port_resume,
> - * which reside in drivers/usb/core/usb.h. Skip for now. */
> +/*
> + * These functions need usb_port_suspend and usb_port_resume,
> + * which reside in drivers/usb/core/usb.h. Skip for now.
> + */
>
> static int stub_suspend(struct usb_device *udev, pm_message_t message)
> {
> - dev_dbg(&udev->dev, "stub_suspend\n");
> + dev_dbg(&udev->dev, "stub suspend\n");
>
> return 0;
> }
>
> static int stub_resume(struct usb_device *udev, pm_message_t message)
> {
> - dev_dbg(&udev->dev, "stub_resume\n");
> + dev_dbg(&udev->dev, "stub resume\n");
>
> return 0;
> }
> --
> 2.34.1
>
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- Your patch did many different things all at once, making it difficult
to review. All Linux kernel patches need to only do one thing at a
time. If you need to do multiple things (such as clean up all coding
style issues in a file/driver), do it in a sequence of patches, each
one doing only one thing. This will make it easier to review the
patches to ensure that they are correct, and to help alleviate any
merge issues that larger patches can cause.
- You did not specify a description of why the patch is needed, or
possibly, any description at all, in the email body. Please read the
section entitled "The canonical patch format" in the kernel file,
Documentation/process/submitting-patches.rst for what is needed in
order to properly describe the change.
- You did not write a descriptive Subject: for the patch, allowing Greg,
and everyone else, to know what this patch is all about. Please read
the section entitled "The canonical patch format" in the kernel file,
Documentation/process/submitting-patches.rst for what a proper
Subject: line should look like.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
