public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jaya Durga <jayad@cdac.in>, gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
	driverdev-devel@linuxdriverproject.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Staging: rtl8712: ieee80211: fixed camelcase coding style issue
Date: Sun, 07 May 2017 16:07:22 -0700	[thread overview]
Message-ID: <1494198442.31950.50.camel@perches.com> (raw)
In-Reply-To: <1494184510-21422-1-git-send-email-jayad@cdac.in>

On Mon, 2017-05-08 at 00:45 +0530, Jaya Durga wrote:
> Fixed coding style issue

Please list the various renames you are doing.

BeaconPeriod	-> beacon_period
DSConfig	-> ds_config
ATIMWindow	-> atim_window

etc...

And it's generally better to do these while avoiding
changing line breaks.


There are maintainers that also would want these
renames done in individual separate patches.

> diff --git a/drivers/staging/rtl8712/ieee80211.c b/drivers/staging/rtl8712/ieee80211.c
[]
> @@ -174,7 +174,8 @@ int r8712_generate_ie(struct registry_priv *pregistrypriv)
>  	sz += 8;
>  	ie += sz;
>  	/*beacon interval : 2bytes*/
> -	*(__le16 *)ie = cpu_to_le16((u16)pdev_network->Configuration.BeaconPeriod);
> +	*(__le16 *)ie = cpu_to_le16(
> +				(u16)pdev_network->configuration.beacon_period);

It's also frequently better to use a temporary pointer
and convert these relatively long indirections to
something simpler like:

	<whatever_type> *cfg = &pdev_network->configuration;

	*(__le16 *)ie = cpu_to_le16(cfg->beacon_period);

etc...

in separate patches.

      reply	other threads:[~2017-05-07 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07 19:15 [PATCH 3/3] Staging: rtl8712: ieee80211: fixed camelcase coding style issue Jaya Durga
2017-05-07 23:07 ` Joe Perches [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=1494198442.31950.50.camel@perches.com \
    --to=joe@perches.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=florian.c.schilhabel@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jayad@cdac.in \
    --cc=linux-kernel@vger.kernel.org \
    /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