From: "M. Vefa Bicakci" <m.v.b@runbox.com>
To: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Cc: Jes.Sorensen@redhat.com, joe@perches.com,
Larry.Finger@lwfinger.net, gregkh@linuxfoundation.org,
mail@beyermatthias.de, m.v.b@runbox.com
Subject: [PATCH v3 09/15] staging: rtl8723au: that open brace should be on the previous line
Date: Thu, 19 Mar 2015 00:39:12 -0400 [thread overview]
Message-ID: <1426739958-18949-10-git-send-email-m.v.b@runbox.com> (raw)
In-Reply-To: <1426739958-18949-1-git-send-email-m.v.b@runbox.com>
Correct two instances of the checkpatch.pl error indicating that the
opening curly braces should not be on new lines:
ERROR: that open brace { should be on the previous line
v3: Make sure that all edited lines are at most 80 characters wide.
Signed-off-by: M. Vefa Bicakci <m.v.b@runbox.com>
---
drivers/staging/rtl8723au/core/rtw_security.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_security.c b/drivers/staging/rtl8723au/core/rtw_security.c
index 803f8965a4..0557a0df52 100644
--- a/drivers/staging/rtl8723au/core/rtw_security.c
+++ b/drivers/staging/rtl8723au/core/rtw_security.c
@@ -760,8 +760,8 @@ int rtw_tkip_decrypt23a(struct rtw_adapter *padapter,
*((u32 *)crc) = le32_to_cpu(getcrc32(payload, length - 4));
- if (crc[3] != payload[length - 1] || crc[2] != payload[length - 2] || crc[1] != payload[length - 3] || crc[0] != payload[length - 4])
- {
+ if (crc[3] != payload[length - 1] || crc[2] != payload[length - 2] ||
+ crc[1] != payload[length - 3] || crc[0] != payload[length - 4]) {
RT_TRACE(_module_rtl871x_security_c_, _drv_err_, ("rtw_wep_decrypt23a:icv error crc[3](%x)!= payload[length-1](%x) || crc[2](%x)!= payload[length-2](%x) || crc[1](%x)!= payload[length-3](%x) || crc[0](%x)!= payload[length-4](%x)\n",
crc[3], payload[length - 1], crc[2], payload[length - 2], crc[1], payload[length - 3], crc[0], payload[length - 4]));
res = _FAIL;
@@ -845,8 +845,7 @@ static void next_key(u8 *key, int round)
{
u8 rcon;
u8 sbox_key[4];
- u8 rcon_table[12] =
- {
+ u8 rcon_table[12] = {
0x01, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, 0x80,
0x1b, 0x36, 0x36, 0x36
};
--
2.1.4
next prev parent reply other threads:[~2015-03-19 4:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 4:39 [PATCH v3 00/15] checkpatch clean-up of rtl8723au's rtw_security.c M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 01/15] staging: rtl8723au: Reformat whitespace to increase readability M. Vefa Bicakci
2015-03-26 12:18 ` Greg KH
2015-03-28 12:39 ` M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 02/15] staging: rtl8723au: Fix "before/around/after" whitespace issues M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 03/15] staging: rtl8723au: else should follow close brace M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 04/15] staging: rtl8723au: Fix the indentation of two lines M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 05/15] staging: rtl8723au: Reorganize a few functions to remove indentation M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 06/15] staging: rtl8723au: else is not generally useful after a return M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 07/15] staging: rtl8723au: Remove unneeded curly braces M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 08/15] staging: rtl8723au: trailing statements should be on next line M. Vefa Bicakci
2015-03-19 4:39 ` M. Vefa Bicakci [this message]
2015-03-19 4:39 ` [PATCH v3 10/15] staging: rtl8723au: No spaces at the start of a line M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 11/15] staging: rtl8723au: Adjust whitespace in and around comments M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 12/15] staging: rtl8723au: suspect code indent for conditional statements M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 13/15] staging: rtl8723au: Rework two byte array comparisons M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 14/15] staging: rtl8723au: Use __func__ in trace logs M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 15/15] staging: rtl8723au: Remove unneeded comments M. Vefa Bicakci
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=1426739958-18949-10-git-send-email-m.v.b@runbox.com \
--to=m.v.b@runbox.com \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mail@beyermatthias.de \
/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
all inboxes | Powered by JetHome®