From: Joe Perches <joe@perches.com>
To: Aviya Erenfeld <aviyae42@gmail.com>,
gregkh@linuxfoundation.org, goudapatilk@gmail.com,
insafonov@gmail.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] staging: rtl8188eu: Shorten lines over 80 chars
Date: Mon, 12 Jun 2017 23:03:36 -0700 [thread overview]
Message-ID: <1497333816.18751.9.camel@perches.com> (raw)
In-Reply-To: <70808b1d-6494-ec20-ec6c-0ff26204ea99@gmail.com>
On Tue, 2017-06-13 at 08:52 +0300, Aviya Erenfeld wrote:
> Shorten lines over 80 chars
Most of these changes are not useful.
Style nits if 80 columns are _really_ desired.
> diff --git a/drivers/staging/rtl8188eu/core/rtw_sta_mgt.c b/drivers/staging/rtl8188eu/core/rtw_sta_mgt.c
[]
> @@ -157,7 +164,8 @@ u32 _rtw_free_sta_priv(struct sta_priv *pstapriv)
> plist = plist->next;
>
> for (i = 0; i < 16; i++) {
> - preorder_ctrl = &psta->recvreorder_ctrl[i];
> + preorder_ctrl =
> + &psta->recvreorder_ctrl[i];
> del_timer_sync(&preorder_ctrl->reordering_ctrl_timer);
This is harder to read.
> @@ -453,14 +471,16 @@ u32 rtw_init_bcmc_stainfo(struct adapter *padapter)
> {
> struct sta_info *psta;
> u32 res = _SUCCESS;
> - unsigned char bcast_addr[ETH_ALEN] = {0xff, 0xff, 0xff, 0xff, 0xff, 0xff};
> + unsigned char bcast_addr[ETH_ALEN] = {0xff, 0xff, 0xff, 0xff, 0xff,
> + 0xff};
More common would be
unsigned char bcast_addr[ETH_ALEN] = {
0xff, 0xff, 0xff, 0xff, 0xff, 0xff
};
Better still would be to use static const.
Best would be to see if bcast_addr is needed at all.
prev parent reply other threads:[~2017-06-13 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 5:49 [PATCH v2 0/3] Fix some style issues Aviya Erenfeld
2017-06-13 5:50 ` [PATCH v2 1/3] staging: rtl8188eu: Remove redundant parenthesis Aviya Erenfeld
2017-06-13 9:22 ` Greg KH
2017-06-13 5:51 ` [PATCH v2 2/3] staging: rtl8188eu: Remove unneeded blank lines Aviya Erenfeld
2017-06-13 5:52 ` [PATCH v2 3/3] staging: rtl8188eu: Shorten lines over 80 chars Aviya Erenfeld
2017-06-13 6:03 ` 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=1497333816.18751.9.camel@perches.com \
--to=joe@perches.com \
--cc=aviyae42@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=goudapatilk@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=insafonov@gmail.com \
--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
Powered by JetHome