linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org
Subject: [PATCH 11/13 net-next] net: mac80211.h: drop duplicate words in comments
Date: Tue, 14 Jul 2020 19:59:12 -0700	[thread overview]
Message-ID: <20200715025914.28091-11-rdunlap@infradead.org> (raw)
In-Reply-To: <20200715025914.28091-1-rdunlap@infradead.org>

Drop doubled words "are" and "by" in comments.
Change doubled "to to" to "to the".

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
---
 include/net/mac80211.h |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

--- linux-next-20200714.orig/include/net/mac80211.h
+++ linux-next-20200714/include/net/mac80211.h
@@ -2727,7 +2727,7 @@ void ieee80211_free_txskb(struct ieee802
  * for devices that support offload of data packets (e.g. ARP responses).
  *
  * Mac80211 drivers should set the @NL80211_EXT_FEATURE_CAN_REPLACE_PTK0 flag
- * when they are able to replace in-use PTK keys according to to following
+ * when they are able to replace in-use PTK keys according to the following
  * requirements:
  * 1) They do not hand over frames decrypted with the old key to
       mac80211 once the call to set_key() with command %DISABLE_KEY has been
@@ -4709,7 +4709,7 @@ void ieee80211_tx_status_irqsafe(struct
  *
  * Call this function for all transmitted data frames after their transmit
  * completion. This callback should only be called for data frames which
- * are are using driver's (or hardware's) offload capability of encap/decap
+ * are using driver's (or hardware's) offload capability of encap/decap
  * 802.11 frames.
  *
  * This function may not be called in IRQ context. Calls to this function
@@ -6344,7 +6344,7 @@ void ieee80211_unreserve_tid(struct ieee
  *
  * Note that this must be called in an rcu_read_lock() critical section,
  * which can only be released after the SKB was handled. Some pointers in
- * skb->cb, e.g. the key pointer, are protected by by RCU and thus the
+ * skb->cb, e.g. the key pointer, are protected by RCU and thus the
  * critical section must persist not just for the duration of this call
  * but for the duration of the frame handling.
  * However, also note that while in the wake_tx_queue() method,

  parent reply	other threads:[~2020-07-15  2:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  2:59 [PATCH 01/13 net-next] net: nl80211.h: drop duplicate words in comments Randy Dunlap
2020-07-15  2:59 ` [PATCH 02/13 net-next] net: wireless.h: drop duplicate word " Randy Dunlap
2020-07-15  2:59 ` [PATCH 03/13 net-next] net: qed: drop duplicate words " Randy Dunlap
2020-07-15  2:59 ` [PATCH 04/13 net-next] net: skbuff.h: " Randy Dunlap
2020-07-15  2:59 ` [PATCH 05/13 net-next] net: wimax: fix " Randy Dunlap
2020-07-15  2:59 ` [PATCH 06/13 net-next] net: 9p: drop duplicate word in comment Randy Dunlap
2020-07-15  2:59 ` [PATCH 07/13 net-next] net: caif: drop duplicate words in comments Randy Dunlap
2020-07-15  2:59 ` [PATCH 08/13 net-next] net: cfg80211.h: " Randy Dunlap
2020-07-15  2:59 ` [PATCH 09/13 net-next] net: dsa.h: drop duplicate word in comment Randy Dunlap
2020-07-15  2:59 ` [PATCH 10/13 net-next] net: ip6_fib.h: " Randy Dunlap
2020-07-15  2:59 ` Randy Dunlap [this message]
2020-07-15  2:59 ` [PATCH 12/13 net-next] net: regulatory.h: " Randy Dunlap
2020-07-15  2:59 ` [PATCH 13/13 net-next] net: sctp: drop duplicate words in comments Randy Dunlap
2020-07-15 15:48 ` [PATCH 01/13 net-next] net: nl80211.h: " Jakub Kicinski
2020-07-15 16:06   ` Johannes Berg
2020-07-15 16:11     ` Randy Dunlap
2020-07-15 16:12   ` Joe Perches
2020-07-15 16:18     ` Randy Dunlap
2020-07-15 16:27       ` Jakub Kicinski

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=20200715025914.28091-11-rdunlap@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).