public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Khadija Kamran <kamrankhadijadj@gmail.com>
Cc: outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] staging: rtl8192u: remove code from comments
Date: Sat, 25 Mar 2023 13:22:35 +0100	[thread overview]
Message-ID: <ZB7ni6yQdTvuhOIW@kroah.com> (raw)
In-Reply-To: <70aacb99144b4c776f8efa4c47a8423c58a9454f.1679744684.git.kamrankhadijadj@gmail.com>

On Sat, Mar 25, 2023 at 05:13:18PM +0500, Khadija Kamran wrote:
> Writing code in comments is generally not considered a good coding
> practice.
> Remove all the code comments from the file.

How about something like:
	Remove all of the commented out code lines as they are not being
	used and can be brought back in the future if they are ever
	needed again.

And the subject reads a bit odd too, how about:
	staging: rtl8192u: remove commented out code

> 
> Signed-off-by: Khadija Kamran <kamrankhadijadj@gmail.com>
> ---
>  drivers/staging/rtl8192u/r8192U_dm.c | 127 +--------------------------
>  1 file changed, 2 insertions(+), 125 deletions(-)
> 
> diff --git a/drivers/staging/rtl8192u/r8192U_dm.c b/drivers/staging/rtl8192u/r8192U_dm.c
> index 885c5966342f..f210ede8b1c7 100644
> --- a/drivers/staging/rtl8192u/r8192U_dm.c
> +++ b/drivers/staging/rtl8192u/r8192U_dm.c
> @@ -50,11 +50,9 @@ static	void	dm_init_bandwidth_autoswitch(struct net_device *dev);
>  static	void	dm_bandwidth_autoswitch(struct net_device *dev);
>  
>  /* DM --> TX power control */
> -/*static	void	dm_initialize_txpower_tracking(struct net_device *dev);*/
>  
>  static	void	dm_check_txpower_tracking(struct net_device *dev);
>  
> -/*static	void	dm_txpower_reset_recovery(struct net_device *dev);*/
>  

The extra blank lines can now go away as well, at the same time, right?

thanks,

greg k-h

      reply	other threads:[~2023-03-25 12:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25 12:13 [PATCH 0/3] staging: rtl8192u: clean up comments in r8192U_dm.c Khadija Kamran
2023-03-25 12:13 ` [PATCH 1/3] staging: rtl8192u: reformat block comments Khadija Kamran
2023-03-25 12:23   ` Greg KH
2023-03-25 12:31     ` Khadija Kamran
2023-03-25 12:13 ` [PATCH 2/3] staging: rtl8192u: remove change history from comments Khadija Kamran
2023-03-25 12:23   ` Greg KH
2023-03-25 14:04     ` Julia Lawall
2023-03-25 12:13 ` [PATCH 3/3] staging: rtl8192u: remove code " Khadija Kamran
2023-03-25 12:22   ` 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=ZB7ni6yQdTvuhOIW@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kamrankhadijadj@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    /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