All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: anushkacharu9@gmail.com
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] staging: rtl8192e: fix line over 80 caharacters
Date: Thu, 21 Mar 2019 19:25:43 +0100	[thread overview]
Message-ID: <20190321182543.GA10586@kroah.com> (raw)
In-Reply-To: <20190321175955.4921-1-anushkacharu9@gmail.com>

On Thu, Mar 21, 2019 at 11:29:55PM +0530, anushkacharu9@gmail.com wrote:
> From: Anushka Shukla <anushkacharu9@gmail.com>
> 
>  -Fix line over 80 character issue in dot11d.c file 
>  -Define a new variable tri_first_channel of u8  data type. 
>  -Assign triple->first_channel as tri_first_channel
> 
> Signed-off-by: Anushka Shukla <anushkacharu9@gmail.com>
> ---
>  drivers/staging/rtl8192e/dot11d.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/rtl8192e/dot11d.c b/drivers/staging/rtl8192e/dot11d.c
> index 68f53013cb95..62f34b38be21 100644
> --- a/drivers/staging/rtl8192e/dot11d.c
> +++ b/drivers/staging/rtl8192e/dot11d.c
> @@ -140,12 +140,13 @@ void dot11d_update_country(struct rtllib_device *dev, u8 *address,
>  				    __func__);
>  			return;
>  		}
> +		u8 tri_first_channel = triple->first_channel;

How about just "first_channel"?

Makes more sense, "tri_" isn't that descriptive here.

But, you need to actually build this code and notice how you have a
build warning, that's not ok :(

thanks,

greg k-h


      reply	other threads:[~2019-03-21 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 17:59 [PATCH] staging: rtl8192e: fix line over 80 caharacters anushkacharu9
2019-03-21 18:25 ` 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=20190321182543.GA10586@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=anushkacharu9@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.