public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ravi Kumar kairi <kumarkairiravi@gmail.com>
Cc: dpenkler@gmail.com, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, kuba@kernel.org,
	dan.carpenter@linaro.org, rmk+kernel@armlinux.org.uk
Subject: Re: [PATCH 0/4] staging:gpib:agilent_82350b:Cleanup and spelling fixes
Date: Mon, 17 Feb 2025 11:31:54 +0100	[thread overview]
Message-ID: <2025021729-angular-ignition-0858@gregkh> (raw)
In-Reply-To: <20250217100526.49495-1-kumarkairiravi@gmail.com>

On Mon, Feb 17, 2025 at 03:35:09PM +0530, Ravi Kumar kairi wrote:
> From: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
> 
> 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 a empty line in if{} which was casuing it be read as single
> line
> 
> These are minor changes aimed at improving code readability and maintainability.
> 
> I appreciate your time in reviewing this series.
> 
> Thanks,  
> Ravi Kumar Kairi
> 
> 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
> 
> 

Something went wrong with your submission here, look at how these show
up on lore.kernel.org and in my inbox:

 Feb 17 Ravi Kumar kair (0.9K) ┬─>[PATCH 4/4] [PATCH V2 4/4] staging:gpib:agilent_82350b: Fix Indent issue with block
 Feb 17 Ravi Kumar kair (1.5K) ├─>[PATCH 3/4] [PATCH V2 3/4] staging:gpib:agilent_82350b:Removed blank line
 Feb 17 Ravi Kumar kair (1.5K) ├─>[PATCH 2/2] [PATCH V2 3/4] staging:gpib:agilent_82350b:Removed blank line
 Feb 17 Ravi Kumar kair (3.0K) ├─>[PATCH 2/4] [PATCH V2 2/4] staging:gpib:agilent_82350b: Removed commented out code
 Feb 17 Ravi Kumar kair (3.0K) └─>[PATCH 1/2] [PATCH V2 2/4] staging:gpib:agilent_82350b: Removed commented out code
 Feb 17 Ravi Kumar kair (0.8K) [PATCH 0/4] staging:gpib:agilent_82350b:Cleanup and spelling fixes
 Feb 17 Ravi Kumar kair (0.9K) └─>[PATCH 1/4] [PATCH V2 1/4] staging:gpib:agilent_82350b: Fixed spelling error

I count 6 patches in a patch series of 4?  And the threading is broken
in a very odd way?

Please fix up and send a proper v3 series.

thanks,

greg k-h

      parent reply	other threads:[~2025-02-17 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 10:05 [PATCH 0/4] staging:gpib:agilent_82350b:Cleanup and spelling fixes Ravi Kumar kairi
2025-02-17 10:05 ` [PATCH 1/4] [PATCH V2 1/4] staging:gpib:agilent_82350b: Fixed spelling error Ravi Kumar kairi
2025-02-17 10:31 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025021729-angular-ignition-0858@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@linaro.org \
    --cc=dpenkler@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kumarkairiravi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=rmk+kernel@armlinux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox