Re: [PATCH v3 0/4] staging:gpib:agilent_82350b: Code cleanup, spelling fixes

[Greg KH <gregkh@linuxfoundation.org>]

On Mon, Feb 17, 2025 at 04:00:34PM +0530, Ravi Kumar kairi wrote:
> From: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
> 
> This patch series addresses the following changes:
> 1. Fixing spelling mistakes such as "havn't" → "haven't"
> 2. Removing unnecessary commented-out code
> 3. Cleaning up whitespace and formatting inconsistencies
> 4. Removing an empty line in if{} which was causing it to be read as a single line
> 
> These are minor changes aimed at improving code readability and maintainability.
> 
> I appreciate your time in reviewing this series. and I'm deeply sorry
> for the spam beacuse I messed up last time I sumbiited
> Thanks,
> Ravi Kumar Kairi (4):
>   staging:gpib:agilent_82350b: Fixed spelling error
>   staging:gpib:agilent_82350b: Removed commented out code
>   staging:gpib:agilent_82350b:Removed blank line
>   staging:gpib:agilent_82350b: Fix Indent issue with block
> 
>  .../staging/gpib/agilent_82350b/agilent_82350b.c | 16 +---------------
>  1 file changed, 1 insertion(+), 15 deletions(-)
> 
> -- 
> 2.48.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/process/submitting-patches.rst 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