[PATCH] Fixed Spelling error

[PATCH] Fixed Spelling error

[Sumya Hoque]

diff --git a/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt b/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt
index 93fec32a1188..faccee68f603 100644
--- a/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt
+++ b/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt
@@ -30,7 +30,7 @@ provide for a handler)
 GP_SAMPLE register is at 0x35C058
 
 Bits are then right shifted into the GP_SAMPLE register at the specified
-rate; you get an interrupt when a full DWORD is recieved.
+rate; you get an interrupt when a full DWORD is received.
 You need to recover the actual RC5 bits out of the (oversampled) IR sensor
 bits. (Hint: look for the 0/1and 1/0 crossings of the RC5 bi-phase data)  An
 actual raw RC5 code will span 2-3 DWORDS, depending on the actual alignment.
-- 
2.34.1

Re: [PATCH] Fixed Spelling error

[Greg KH]

On Tue, Feb 18, 2025 at 03:28:34AM +0000, Sumya Hoque wrote:
> diff --git a/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt b/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt
> index 93fec32a1188..faccee68f603 100644
> --- a/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt
> +++ b/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt
> @@ -30,7 +30,7 @@ provide for a handler)
>  GP_SAMPLE register is at 0x35C058
>  
>  Bits are then right shifted into the GP_SAMPLE register at the specified
> -rate; you get an interrupt when a full DWORD is recieved.
> +rate; you get an interrupt when a full DWORD is received.
>  You need to recover the actual RC5 bits out of the (oversampled) IR sensor
>  bits. (Hint: look for the 0/1and 1/0 crossings of the RC5 bi-phase data)  An
>  actual raw RC5 code will span 2-3 DWORDS, depending on the actual alignment.
> -- 
> 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 does not have a Signed-off-by: line.  Please read the
  kernel file, Documentation/process/submitting-patches.rst and resend
  it after adding that line.  Note, the line needs to be in the body of
  the email, before the patch, not at the bottom of the patch or in the
  email signature.

- 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