All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoeb Mithaiwala <zoebm@google.com>
To: dan.carpenter@oracle.com
Cc: greg@kroah.com, trivial@kernel.org, linux-kernel@vger.kernel.org,
	 linux-staging@lists.linux.dev,
	Zoeb Mithaiwala <zoebm@google.com>
Subject: [PATCH v3 3/3] Staging: rtl8712: Fixes a camel case variable name style issue
Date: Mon, 22 Nov 2021 17:03:35 +0000	[thread overview]
Message-ID: <20211122170335.1468730-1-zoebm@google.com> (raw)
In-Reply-To: <20211122103931.GA6514@kadam>

Changes the names of variables in rtl871x_security from camel case to
snake case to match coding style.

Signed-off-by: Zoeb Mithaiwala <zoebm@google.com>
---
Changes in v3:
  - Fixes commit messages for patch.
  - Uses the same variable names in header file as implementation files.
Changes in v2:
  - Changes the variable name from nBytesInM to bytes_in_m.
  - Removes changes to other variables in the file.
---
 drivers/staging/rtl8712/rtl871x_security.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/rtl8712/rtl871x_security.h b/drivers/staging/rtl8712/rtl871x_security.h
index 1de662940417..81262e68bee1 100644
--- a/drivers/staging/rtl8712/rtl871x_security.h
+++ b/drivers/staging/rtl8712/rtl871x_security.h
@@ -200,11 +200,11 @@ void seccalctkipmic(
 	u8  *header,
 	u8  *data,
 	u32  data_len,
-	u8  *Miccode,
+	u8  *mic_code,
 	u8   priority);
 
 void r8712_secmicsetkey(struct mic_data *pmicdata, u8 *key);
-void r8712_secmicappend(struct mic_data *pmicdata, u8 *src, u32 nBytes);
+void r8712_secmicappend(struct mic_data *pmicdata, u8 *src, u32 nbytes);
 void r8712_secgetmic(struct mic_data *pmicdata, u8 *dst);
 u32 r8712_aes_encrypt(struct _adapter *padapter, u8 *pxmitframe);
 u32 r8712_tkip_encrypt(struct _adapter *padapter, u8 *pxmitframe);
-- 
2.20.1


  reply	other threads:[~2021-11-22 17:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20  8:06 [PATCH] Staging: rtl8712: rtl871x_security: fixed a camel case variable name coding style issue Zoeb Mithaiwala
2021-11-20  8:26 ` Greg KH
2021-11-20 11:11   ` [PATCH 2/2] " Zoeb Mithaiwala
2021-11-22 10:39     ` Dan Carpenter
2021-11-22 17:03       ` Zoeb Mithaiwala [this message]
2021-11-24 10:01         ` [PATCH v3 3/3] Staging: rtl8712: Fixes a camel case variable name " Greg KH
2021-11-25 17:07           ` Zoeb Mithaiwala
2021-11-25 17:14             ` Greg KH
2021-11-24 10:00     ` [PATCH 2/2] Staging: rtl8712: rtl871x_security: fixed a camel case variable name coding " Greg KH
2021-11-22 15:22 ` [PATCH] " kernel test robot
2021-11-22 15:22   ` kernel test robot
2021-11-26  8:54 ` kernel test robot
2021-11-26  8:54   ` kernel test robot

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=20211122170335.1468730-1-zoebm@google.com \
    --to=zoebm@google.com \
    --cc=dan.carpenter@oracle.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=trivial@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 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.