[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2023101313-aftermost-skydiver-c587@gregkh>
Date: Fri, 13 Oct 2023 08:29:37 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: chenguohua@...i.cn
Cc: jirislaby@...nel.org, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org
Subject: Re: [PATCH] vt: Clean up errors in selection.h
On Fri, Oct 13, 2023 at 10:55:01AM +0800, chenguohua@...i.cn wrote:
> Fix the following errors reported by checkpatch:
>
> ERROR: "foo * bar" should be "foo *bar"
>
> Signed-off-by: GuoHua Cheng <chenguohua@...i.cn>
> ---
> include/linux/selection.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/selection.h b/include/linux/selection.h
> index 170ef28ff26b..3bff95699083 100644
> --- a/include/linux/selection.h
> +++ b/include/linux/selection.h
> @@ -22,7 +22,7 @@ extern int set_selection_kernel(struct tiocl_selection *v,
> extern int paste_selection(struct tty_struct *tty);
> extern int sel_loadlut(char __user *p);
> extern int mouse_reporting(void);
> -extern void mouse_report(struct tty_struct * tty, int butt, int mrx, int mry);
> +extern void mouse_report(struct tty_struct *tty, int butt, int mrx, int mry);
>
> bool vc_is_sel(struct vc_data *vc);
>
> --
> 2.17.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:
- It looks like you did not use your name for the patch on either
the Signed-off-by: line, or the From: line (both of which have to
match). Please read the kernel file,
Documentation/process/submitting-patches.rst for how to do this
correctly.
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