Correct terminology in ieee80211_input skb_copy comment

git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3585 0192ed92-7a03-0410-a25b-9323aeb14dbd

diff --git a/net80211/ieee80211_input.c b/net80211/ieee80211_input.c
index 35e29263813a490df1f9078b44ced87088750bb8..2820e9c89f4335a8a851e720cb483195c62f6efb 100644 (file)
--- a/net80211/ieee80211_input.c
+++ b/net80211/ieee80211_input.c
@@ -238,13 +238,12 @@ ieee80211_input(struct ieee80211vap * vap, struct ieee80211_node *ni_or_null,
                vap->iv_stats.is_rx_tooshort++;
                goto out;
        }
-       /* Clone the SKB... we assume somewhere in this driver that we 'own'
+       /* Copy the SKB... we assume somewhere in this driver that we 'own'
         * the skbuff passed into hard start and we do a lot of messing with it
         * but bridges under some cases will not clone for the first pass of skb
         * to a bridge port, but will then clone for subsequent ones.  This is 
         * odd behavior but it means that if we have trashed the skb we are given
-        * then other ports get clones of the residual garbage.
-        */
+        * then other ports get clones of the residual garbage. */
        if ((skb = skb_copy(original_skb, GFP_ATOMIC)) == NULL) {
                vap->iv_devstats.tx_dropped++;
                original_skb = NULL; /* protect caller's skb */