[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220209150242.2292183-1-trix@redhat.com>
Date: Wed, 9 Feb 2022 07:02:42 -0800
From: trix@...hat.com
To: davem@...emloft.net, kuba@...nel.org, alobakin@...me,
edumazet@...gle.com, pabeni@...hat.com, vvs@...tuozzo.com,
cong.wang@...edance.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Tom Rix <trix@...hat.com>
Subject: [PATCH] skbuff: cleanup double word in comment
From: Tom Rix <trix@...hat.com>
Remove the second 'to'.
Signed-off-by: Tom Rix <trix@...hat.com>
---
net/core/skbuff.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
index 0118f0afaa4fc..9d0388bed0c1d 100644
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -681,7 +681,7 @@ static void skb_release_data(struct sk_buff *skb)
* while trying to recycle fragments on __skb_frag_unref() we need
* to make one SKB responsible for triggering the recycle path.
* So disable the recycling bit if an SKB is cloned and we have
- * additional references to to the fragmented part of the SKB.
+ * additional references to the fragmented part of the SKB.
* Eventually the last SKB will have the recycling bit set and it's
* dataref set to 0, which will trigger the recycling
*/
--
2.26.3
Powered by blists - more mailing lists