All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jules Irenge <jbi.octave@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v1 3/3] staging: rtl8192e: fix line over 80 characters warning
Date: Mon, 11 Mar 2019 04:07:37 +0100	[thread overview]
Message-ID: <20190311030737.GB17063@kroah.com> (raw)
In-Reply-To: <20190311000702.12740-4-jbi.octave@gmail.com>

On Mon, Mar 11, 2019 at 12:07:02AM +0000, Jules Irenge wrote:
> Replace dot11d_info with dt1d_inf to fix checkpatch.pl warning
>  Issue found by checkpatch.pl:
>  "WARNING: line over 80 characters"
> 
> Signed-off-by: Jules Irenge <jbi.octave@gmail.com>
> ---
>  drivers/staging/rtl8192e/dot11d.c | 48 +++++++++++++++----------------
>  1 file changed, 24 insertions(+), 24 deletions(-)
> 
> diff --git a/drivers/staging/rtl8192e/dot11d.c b/drivers/staging/rtl8192e/dot11d.c
> index 721892cef3a7..17738859b197 100644
> --- a/drivers/staging/rtl8192e/dot11d.c
> +++ b/drivers/staging/rtl8192e/dot11d.c
> @@ -37,14 +37,14 @@ static struct channel_list channel_array[] = {
>  
>  void dot11d_init(struct rtllib_device *ieee)
>  {
> -	struct rt_dot11d_info *dot11d_info = GET_DOT11D_INFO(ieee);
> +	struct rt_dot11d_info *dt1d_inf = GET_DOT11D_INFO(ieee);

No, the original variable name is fine, don't shorten things for no good
reason.

>  
> -	dot11d_info->enabled = false;
> +	dt1d_inf->enabled = false;
>  
> -	dot11d_info->state = DOT11D_STATE_NONE;
> -	dot11d_info->country_len = 0;
> -	memset(dot11d_info->channel_map, 0, MAX_CHANNEL_NUMBER + 1);
> -	memset(dot11d_info->max_tx_power_list, 0xFF, MAX_CHANNEL_NUMBER + 1);
> +	dt1d_inf->state = DOT11D_STATE_NONE;
> +	dt1d_inf->country_len = 0;
> +	memset(dt1d_inf->channel_map, 0, MAX_CHANNEL_NUMBER + 1);
> +	memset(dt1d_inf->max_tx_power_list, 0xFF, MAX_CHANNEL_NUMBER + 1);
>  	RESET_CIE_WATCHDOG(ieee);
>  }
>  EXPORT_SYMBOL(dot11d_init);

None of those lines were over 80 characters, so why did you change
anything here?

> @@ -93,29 +93,29 @@ EXPORT_SYMBOL(dot11d_channel_map);
>  
>  void dot11d_reset(struct rtllib_device *ieee)
>  {
> -	struct rt_dot11d_info *dot11d_info = GET_DOT11D_INFO(ieee);
> +	struct rt_dot11d_info *dt1d_inf = GET_DOT11D_INFO(ieee);
>  	u32 i;
>  
> -	memset(dot11d_info->channel_map, 0, MAX_CHANNEL_NUMBER + 1);
> -	memset(dot11d_info->max_tx_power_list, 0xFF, MAX_CHANNEL_NUMBER + 1);
> +	memset(dt1d_inf->channel_map, 0, MAX_CHANNEL_NUMBER + 1);
> +	memset(dt1d_inf->max_tx_power_list, 0xFF, MAX_CHANNEL_NUMBER + 1);
>  	for (i = 1; i <= 11; i++)
> -		(dot11d_info->channel_map)[i] = 1;
> +		(dt1d_inf->channel_map)[i] = 1;
>  	for (i = 12; i <= 14; i++)
> -		(dot11d_info->channel_map)[i] = 2;
> -	dot11d_info->state = DOT11D_STATE_NONE;
> -	dot11d_info->country_len = 0;
> +		(dt1d_inf->channel_map)[i] = 2;
> +	dt1d_inf->state = DOT11D_STATE_NONE;
> +	dt1d_inf->country_len = 0;
>  	RESET_CIE_WATCHDOG(ieee);
>  }

Same with this function, what is wrong with it as-is?

>  
>  void dot11d_update_country(struct rtllib_device *dev, u8 *address,
>  			   u16 country_len, u8 *country)
>  {
> -	struct rt_dot11d_info *dot11d_info = GET_DOT11D_INFO(dev);
> +	struct rt_dot11d_info *dt1d_inf = GET_DOT11D_INFO(dev);
>  	u8 i, j, number_of_triples, max_channel_number;
>  	struct chnl_txpow_triple *triple;
>  
> -	memset(dot11d_info->channel_map, 0, MAX_CHANNEL_NUMBER + 1);
> -	memset(dot11d_info->max_tx_power_list, 0xFF, MAX_CHANNEL_NUMBER + 1);
> +	memset(dt1d_inf->channel_map, 0, MAX_CHANNEL_NUMBER + 1);
> +	memset(dt1d_inf->max_tx_power_list, 0xFF, MAX_CHANNEL_NUMBER + 1);
>  	max_channel_number = 0;
>  	number_of_triples = (country_len - 3) / 3;
>  	triple = (struct chnl_txpow_triple *)(country + 3);

Same here.

> @@ -135,8 +135,8 @@ void dot11d_update_country(struct rtllib_device *dev, u8 *address,
>  		}
>  
>  		for (j = 0; j < triple->num_channels; j++) {
> -			dot11d_info->channel_map[triple->first_channel + j] = 1;
> -			dot11d_info->max_tx_power_list[triple->first_channel + j] =
> +			dt1d_inf->channel_map[triple->first_channel + j] = 1;
> +			dt1d_inf->max_tx_power_list[triple->first_channel + j] =
>  						 triple->max_tx_power;
>  			max_channel_number = triple->first_channel + j;
>  		}

Ok, that one line is "too long", but really, it is fine as-is, no need
to change it.

> @@ -146,18 +146,18 @@ void dot11d_update_country(struct rtllib_device *dev, u8 *address,
>  
>  	UPDATE_CIE_SRC(dev, address);
>  
> -	dot11d_info->country_len = country_len;
> -	memcpy(dot11d_info->country_buffer, country, country_len);
> -	dot11d_info->state = DOT11D_STATE_LEARNED;
> +	dt1d_inf->country_len = country_len;
> +	memcpy(dt1d_inf->country_buffer, country, country_len);
> +	dt1d_inf->state = DOT11D_STATE_LEARNED;
>  }
>  
>  void dot11d_scan_complete(struct rtllib_device *dev)
>  {
> -	struct rt_dot11d_info *dot11d_info = GET_DOT11D_INFO(dev);
> +	struct rt_dot11d_info *dt1d_inf = GET_DOT11D_INFO(dev);
>  
> -	switch (dot11d_info->state) {
> +	switch (dt1d_inf->state) {
>  	case DOT11D_STATE_LEARNED:
> -		dot11d_info->state = DOT11D_STATE_DONE;
> +		dt1d_inf->state = DOT11D_STATE_DONE;
>  		break;
>  	case DOT11D_STATE_DONE:
>  		dot11d_reset(dev);

Why change these lines?

As was said before, checkpatch is a hint, not a hard rule.  You always
need to think when making changes.

thanks,

greg k-h


      reply	other threads:[~2019-03-11  3:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11  0:06 [PATCH v1 0/3] SPDX cleanups and line over 80 characters fix Jules Irenge
2019-03-11  0:07 ` [PATCH v1 1/3] staging: rtl8192e: add SPDX GPL-2.0+ license identifier Jules Irenge
2019-03-11  3:04   ` Greg KH
2019-03-11 22:15     ` Jules Octave
2019-03-11 22:40       ` Greg KH
2019-03-11 22:55         ` Jules Octave
2019-03-11  0:07 ` [PATCH v1 2/3] staging: rtl8192e: remove license boilerplate text Jules Irenge
2019-03-11  0:07 ` [PATCH v1 3/3] staging: rtl8192e: fix line over 80 characters warning Jules Irenge
2019-03-11  3:07   ` 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=20190311030737.GB17063@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jbi.octave@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.