All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kimberly Brown <kimbrownkd@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 1/3] staging:rtl8192u: Fix misspelling in struct member name - Style
Date: Mon, 22 Oct 2018 13:41:14 -0400	[thread overview]
Message-ID: <4d1bd329f112fb50c5a234cfa12babf868f3b03c.1540229302.git.kimbrownkd@gmail.com> (raw)
In-Reply-To: <cover.1540229302.git.kimbrownkd@gmail.com>

Fix the spelling mistake in the name of struct member
'cmdpacket_frag_thresold'. 'thresold' should be 'threshold'. Issue found
by checkpatch.

This is a coding style change which should have no impact on runtime
code execution.

Signed-off-by: Kimberly Brown <kimbrownkd@gmail.com>
---
 drivers/staging/rtl8192u/r8192U.h          | 2 +-
 drivers/staging/rtl8192u/r819xU_firmware.c | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/rtl8192u/r8192U.h b/drivers/staging/rtl8192u/r8192U.h
index e65a893fd084..ec4de86933ba 100644
--- a/drivers/staging/rtl8192u/r8192U.h
+++ b/drivers/staging/rtl8192u/r8192U.h
@@ -370,7 +370,7 @@ typedef struct _rt_firmare_seg_container {
 } fw_seg_container, *pfw_seg_container;
 typedef struct _rt_firmware {
 	firmware_status_e firmware_status;
-	u16               cmdpacket_frag_thresold;
+	u16               cmdpacket_frag_threshold;
 #define RTL8190_MAX_FIRMWARE_CODE_SIZE  64000
 	u8                firmware_buf[RTL8190_MAX_FIRMWARE_CODE_SIZE];
 	u16               firmware_buf_size;
diff --git a/drivers/staging/rtl8192u/r819xU_firmware.c b/drivers/staging/rtl8192u/r819xU_firmware.c
index c3ea906f3af3..153d4ee0ec07 100644
--- a/drivers/staging/rtl8192u/r819xU_firmware.c
+++ b/drivers/staging/rtl8192u/r819xU_firmware.c
@@ -24,7 +24,7 @@ static void firmware_init_param(struct net_device *dev)
 	struct r8192_priv	*priv = ieee80211_priv(dev);
 	rt_firmware		*pfirmware = priv->pFirmware;
 
-	pfirmware->cmdpacket_frag_thresold = GET_COMMAND_PACKET_FRAG_THRESHOLD(MAX_TRANSMIT_BUFFER_SIZE);
+	pfirmware->cmdpacket_frag_threshold = GET_COMMAND_PACKET_FRAG_THRESHOLD(MAX_TRANSMIT_BUFFER_SIZE);
 }
 
 /*
@@ -49,7 +49,7 @@ static bool fw_download_code(struct net_device *dev, u8 *code_virtual_address,
 
 	firmware_init_param(dev);
 	/* Fragmentation might be required */
-	frag_threshold = pfirmware->cmdpacket_frag_thresold;
+	frag_threshold = pfirmware->cmdpacket_frag_threshold;
 	do {
 		if ((buffer_len - frag_offset) > frag_threshold) {
 			frag_length = frag_threshold;
-- 
2.17.1



  reply	other threads:[~2018-10-22 17:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 17:40 [PATCH 0/3] staging: rtl8192u: Fix misspellings Kimberly Brown
2018-10-22 17:41 ` Kimberly Brown [this message]
2018-10-22 18:06   ` [Outreachy kernel] [PATCH 1/3] staging:rtl8192u: Fix misspelling in struct member name - Style Vaishali Thakkar
2018-10-22 17:42 ` [PATCH 2/3] staging:rtl8192u: Fix misspelling in variable " Kimberly Brown
2018-10-22 17:42 ` [PATCH 3/3] staging:rtl8192u: Fix misspellings in comments " Kimberly Brown
2018-10-22 17:53   ` [Outreachy kernel] " Julia Lawall
2018-10-23  3:17     ` Kimberly Brown
2018-10-23  5:38       ` Julia Lawall
2018-10-23 16:51 ` [PATCH v2 0/3] staging: rtl8192u: Fix misspellings Kimberly Brown
2018-10-23 16:56   ` [PATCH v2 1/3] staging: rtl8192u: Fix misspelling in struct member name - Style Kimberly Brown
2018-10-23 16:57   ` [PATCH v2 2/3] staging: rtl8192u: Fix misspelling in variable " Kimberly Brown
2018-10-23 16:59   ` [PATCH v2 3/3] staging: rtl8192u: Fix misspellings in comments " Kimberly Brown

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=4d1bd329f112fb50c5a234cfa12babf868f3b03c.1540229302.git.kimbrownkd@gmail.com \
    --to=kimbrownkd@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.com \
    /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.