From: John Whitmore <johnfwhitmore@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: devel@driverdev.osuosl.org, insafonov@gmail.com,
baijiaju1990@gmail.com, keescook@chromium.org, joe@perches.com,
colin.king@canonical.com, gregkh@linuxfoundation.org,
John Whitmore <johnfwhitmore@gmail.com>
Subject: [PATCH 2/5] staging: rtl8192u: Use memset to initialize memory, instead of loop.
Date: Wed, 4 Jul 2018 12:59:22 +0100 [thread overview]
Message-ID: <20180704115925.28024-2-johnfwhitmore@gmail.com> (raw)
In-Reply-To: <20180704115925.28024-1-johnfwhitmore@gmail.com>
Replaced memory initialising loop with memset instead.
Suggested-by: Andy Shevchenko
Signed-off-by: John Whitmore <johnfwhitmore@gmail.com>
---
drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c b/drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c
index a549d9678214..327557176625 100644
--- a/drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c
+++ b/drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c
@@ -777,8 +777,7 @@ static u8 HT_PickMCSRate(struct ieee80211_device *ieee, u8 *pOperateMCS)
//legacy rate routine handled at selectedrate
//no MCS rate
- for (i = 0; i <= 15; i++)
- pOperateMCS[i] = 0;
+ memset(pOperateMCS, 0, 16);
break;
case IEEE_N_24G: //assume CCK rate ok
--
2.17.1
next prev parent reply other threads:[~2018-07-04 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 11:59 [PATCH 1/5] staging: rtl8192u: Use __func__ instead of hardcoded string - Style John Whitmore
2018-07-04 11:59 ` John Whitmore [this message]
2018-07-04 11:59 ` [PATCH 3/5] staging: rtl8192u: Remove unused variable John Whitmore
2018-07-04 12:18 ` Dan Carpenter
2018-07-04 11:59 ` [PATCH 4/5] staging: rtl8192u: Remove redundant definitions in header John Whitmore
2018-07-04 11:59 ` [PATCH 5/5] staging: rtl8192u: Refactor for coding style John Whitmore
2018-07-04 12:26 ` Dan Carpenter
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=20180704115925.28024-2-johnfwhitmore@gmail.com \
--to=johnfwhitmore@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=insafonov@gmail.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--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