staging: wlan-ng: Remove repeated words in comments

Remove duplicate words in comments at prism2mib and prism2sta files.

Signed-off-by: Igor Matheus Andrade Torrente <igormtorrente@gmail.com>
Link: https://lore.kernel.org/r/20200803022022.501-1-igormtorrente@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/staging/wlan-ng/prism2mib.c b/drivers/staging/wlan-ng/prism2mib.c
index 7d7d77b04255dcf3e40bfc97d32061cf9836d080..875812a391c97af52c8c9294d7081e8d86367c16 100644 (file)
--- a/drivers/staging/wlan-ng/prism2mib.c
+++ b/drivers/staging/wlan-ng/prism2mib.c
@@ -292,7 +292,7 @@ int prism2mgmt_mibset_mibget(struct wlandevice *wlandev, void *msgp)
        /*
         ** Determine if this is a "mibget" or a "mibset".  If this is a
         ** "mibget", then make sure that the MIB may be read.  Otherwise,
-        ** this is a "mibset" so make make sure that the MIB may be written.
+        ** this is a "mibset" so make sure that the MIB may be written.
         */
 
        isget = (msg->msgcode == DIDMSG_DOT11REQ_MIBGET);

diff --git a/drivers/staging/wlan-ng/prism2sta.c b/drivers/staging/wlan-ng/prism2sta.c
index 8f25496188aa5ee7a78de46b3b64ca9768810e51..e6dcb687e7a1c1ff849fd11cbcb200f0f36a5f9e 100644 (file)
--- a/drivers/staging/wlan-ng/prism2sta.c
+++ b/drivers/staging/wlan-ng/prism2sta.c
@@ -461,7 +461,7 @@ u32 prism2sta_ifstate(struct wlandevice *wlandev, u32 ifstate)
                case WLAN_MSD_FWLOAD:
                        wlandev->msdstate = WLAN_MSD_RUNNING_PENDING;
                        /* Initialize the device+driver for full
-                        * operation. Note that this might me an FWLOAD to
+                        * operation. Note that this might me an FWLOAD
                         * to RUNNING transition so we must not do a chip
                         * or board level reset.  Note that on failure,
                         * the MSD state is set to HWPRESENT because we
@@ -1352,7 +1352,7 @@ void prism2sta_processing_defer(struct work_struct *data)
                 * we get back in range.  We should block transmits and
                 * receives in this state.  Do we need an indication here?
                 * Probably not since a polling user-mode element would
-                * get this status from from p2PortStatus(FD40). What about
+                * get this status from p2PortStatus(FD40). What about
                 * p80211?
                 * Response:
                 * Block Transmits, Ignore receives of data frames