[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YoC09ZabkFUg9qAO@kroah.com>
Date: Sun, 15 May 2022 10:08:21 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Shreenidhi Shedi <yesshedi@...il.com>
Cc: arnd@...db.de, linux-kernel@...r.kernel.org,
Shreenidhi Shedi <sshedi@...are.com>
Subject: Re: [PATCH 2/3] char: lp: remove redundant initialization of err
On Sun, May 15, 2022 at 01:24:54PM +0530, Shreenidhi Shedi wrote:
> err is getting assigned with an appropriate value before returning,
> hence this initialization is unnecessary.
>
> Signed-off-by: Shreenidhi Shedi <sshedi@...are.com>
> ---
> drivers/char/lp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/lp.c b/drivers/char/lp.c
> index e61060f3c..5e8bd8d6c 100644
> --- a/drivers/char/lp.c
> +++ b/drivers/char/lp.c
> @@ -1018,7 +1018,7 @@ static struct parport_driver lp_driver = {
>
> static int __init lp_init(void)
> {
> - int i, err = 0;
> + int i, err;
>
> if (parport_nr[0] == LP_PARPORT_OFF)
> return 0;
> --
> 2.36.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 "real" 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/SubmittingPatches
for how to do this correctly.
- 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