[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YvXyqRGPSMWvCMrw@kroah.com>
Date: Fri, 12 Aug 2022 08:26:49 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Dongliang Mu <dzm91@...t.edu.cn>
Cc: Dongliang Mu <mudongliangabcd@...il.com>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] USB: trancevibrator: remove redundant space
On Fri, Aug 12, 2022 at 02:18:01PM +0800, Dongliang Mu wrote:
> From: Dongliang Mu <mudongliangabcd@...il.com>
>
> remove a redundant space after usb_get_intfdata
>
> Signed-off-by: Dongliang Mu <mudongliangabcd@...il.com>
> ---
> drivers/usb/misc/trancevibrator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/misc/trancevibrator.c b/drivers/usb/misc/trancevibrator.c
> index 26baba3ab7d7..55cb63652eda 100644
> --- a/drivers/usb/misc/trancevibrator.c
> +++ b/drivers/usb/misc/trancevibrator.c
> @@ -106,7 +106,7 @@ static void tv_disconnect(struct usb_interface *interface)
> {
> struct trancevibrator *dev;
>
> - dev = usb_get_intfdata (interface);
> + dev = usb_get_intfdata(interface);
> usb_set_intfdata(interface, NULL);
> usb_put_dev(dev->udev);
> kfree(dev);
> --
> 2.35.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:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/SubmittingPatches for what needs to be done
here to properly describe this.
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
Powered by blists - more mailing lists