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 5/9 v2 net-next] net: caif: drop duplicate words in comments
Date: Wed, 15 Jul 2020 09:42:42 -0700	[thread overview]
Message-ID: <20200715164246.9054-5-rdunlap@infradead.org> (raw)
In-Reply-To: <20200715164246.9054-1-rdunlap@infradead.org>

Drop doubled words "or" and "the" in several comments.

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
---
v2: move wireless patches to a separate patch series.

 include/net/caif/caif_layer.h         |    4 ++--
 include/uapi/linux/caif/caif_socket.h |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

--- linux-next-20200714.orig/include/net/caif/caif_layer.h
+++ linux-next-20200714/include/net/caif/caif_layer.h
@@ -156,7 +156,7 @@ struct cflayer {
 	 *  CAIF packets upwards in the stack.
 	 *	Packet handling rules:
 	 *	      - The CAIF packet (cfpkt) ownership is passed to the
-	 *		called receive function. This means that the the
+	 *		called receive function. This means that the
 	 *		packet cannot be accessed after passing it to the
 	 *		above layer using up->receive().
 	 *
@@ -184,7 +184,7 @@ struct cflayer {
 	 *	CAIF packet downwards in the stack.
 	 *	Packet handling rules:
 	 *	      - The CAIF packet (cfpkt) ownership is passed to the
-	 *		transmit function. This means that the the packet
+	 *		transmit function. This means that the packet
 	 *		cannot be accessed after passing it to the below
 	 *		layer using dn->transmit().
 	 *
--- linux-next-20200714.orig/include/uapi/linux/caif/caif_socket.h
+++ linux-next-20200714/include/uapi/linux/caif/caif_socket.h
@@ -169,7 +169,7 @@ struct sockaddr_caif {
  * @CAIFSO_LINK_SELECT:		Selector used if multiple CAIF Link layers are
  *				available. Either a high bandwidth
  *				link can be selected (CAIF_LINK_HIGH_BANDW) or
- *				or a low latency link (CAIF_LINK_LOW_LATENCY).
+ *				a low latency link (CAIF_LINK_LOW_LATENCY).
  *                              This option is of type __u32.
  *				Alternatively SO_BINDTODEVICE can be used.
  *

  parent reply	other threads:[~2020-07-15 16:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 16:42 [PATCH 1/9 v2 net-next] net: qed: drop duplicate words in comments Randy Dunlap
2020-07-15 16:42 ` [PATCH 2/9 v2 net-next] net: skbuff.h: " Randy Dunlap
2020-07-15 16:42 ` [PATCH 3/9 v2 net-next] net: wimax: fix " Randy Dunlap
2020-07-16  3:34   ` Jakub Kicinski
2020-07-16  3:35     ` Randy Dunlap
2020-07-16  3:50       ` Jakub Kicinski
2020-07-15 16:42 ` [PATCH 4/9 v2 net-next] net: 9p: drop duplicate word in comment Randy Dunlap
2020-07-15 16:42 ` Randy Dunlap [this message]
2020-07-15 16:42 ` [PATCH 6/9 v2 net-next] net: dsa.h: " Randy Dunlap
2020-07-15 16:42 ` [PATCH 7/9 v2 net-next] net: ip6_fib.h: " Randy Dunlap
2020-07-15 16:42 ` [PATCH 8/9 v2 net-next] net: sctp: drop duplicate words in comments Randy Dunlap
2020-07-15 16:42 ` [PATCH 9/9 v2 net-next] net: ipv6: drop duplicate word in comment Randy Dunlap

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=20200715164246.9054-5-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).