mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Sandeep Salwan <salwansandeep5@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gpib: Remove commented-out line entirely (v2)
Date: Thu, 9 Jan 2025 10:43:35 +0300	[thread overview]
Message-ID: <d17e78a2-ad49-42da-a0d4-56c2f28baee4@stanley.mountain> (raw)
In-Reply-To: <20250108211127.13963-1-salwansandeep5@gmail.com>

On Wed, Jan 08, 2025 at 04:11:27PM -0500, Sandeep Salwan wrote:
> Per Greg’s feedback, remove the line instead of leaving it as a comment.
> It's not needed for debugging, so let's delete it completely. Thanks.

This isn't how we typically write commit messages.  Instead say:
This code has some debug code which is commented out.  Delete it.

> 
> Signed-off-by: Sandeep Salwan <salwansandeep5@gmail.com>

There is a specific formula for v2 patches:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/

> ---
>  drivers/staging/gpib/agilent_82350b/agilent_82350b.c | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/drivers/staging/gpib/agilent_82350b/agilent_82350b.c b/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
> index 3cd01613d067..7ba968e24add 100644
> --- a/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
> +++ b/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
> @@ -31,10 +31,6 @@ int agilent_82350b_accel_read(gpib_board_t *board, uint8_t *buffer, size_t lengt
>  	int i, num_fifo_bytes;
>  	//hardware doesn't support checking for end-of-string character when using fifo
>  	if (tms_priv->eos_flags & REOS) {
> -		/*
> -		 * pr_info("ag-rd: using tms9914 read for REOS %x EOS %x\n",tms_priv->eos_flags,
> -		 * tms_priv->eos);
> -		 */
>  		return tms9914_read(board, tms_priv, buffer, length, end, bytes_read);
>  	}

Now that you have deleted the commented out code, the curly braces need
to be deleted as well.  You don't need to mention this in the commit
message.  It is obvious and assumed.

Please send a v3 of this patch.

regards,
dan carpenter


      reply	other threads:[~2025-01-09  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 21:11 Sandeep Salwan
2025-01-09  7:43 ` Dan Carpenter [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=d17e78a2-ad49-42da-a0d4-56c2f28baee4@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=salwansandeep5@gmail.com \
    /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

all inboxes | Powered by JetHome®