Re: [PATCH 00/10] Code style patches for staging/irda

Re: [PATCH 00/10] Code style patches for staging/irda

[Greg KH]

On Sun, Nov 26, 2017 at 01:45:55AM +0300, Mike wrote:
> 
> This is my task from Little Penguin :)

What does that mean?

> 
> Mike (10):
>   trailing whitespace fixed
>   spaces before tabs are fixed
>   trailing */ on a separate line fixed
>   if-else code style fixed
>   space prohibited before that ',' fixed
>   space required before the open parenthesis - fixed
>   code indent should use tabs where possible - fixed
>   spaces required - fixed
>   others not regular and missed errors are fixed
>   lines over 80 characters are fixed
> 
>  drivers/staging/irda/drivers/ali-ircc.c | 1516 +++++++++++++++----------------
>  1 file changed, 722 insertions(+), 794 deletions(-)

Did you read drivers/staging/irda/TODO ?

Re: [PATCH 01/10] trailing whitespace fixed

[Greg KH]

On Sun, Nov 26, 2017 at 01:45:56AM +0300, Mike wrote:
> Signed-off-by: Mike <lameli67@gmail.com>
> ---
>  drivers/staging/irda/drivers/ali-ircc.c | 1002 +++++++++++++++----------------
>  1 file changed, 501 insertions(+), 501 deletions(-)
> 

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 was attached, please place it inline so that it can be
  applied directly from the email message itself.

- 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/SubmittingPatches 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/SubmittingPatches for what a proper Subject: line should
  look like.

- You did not use your real name.  Signed-off-by: and From: has to have
  a real name associated with it.  Use whatever you sign legal documents
  with, no anonymous patches are allowed.

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