From: Rami Rosen <ramirose@gmail.com>
To: davem@davemloft.net
Cc: maxk@qti.qualcomm.com, netdev@vger.kernel.org,
Rami Rosen <ramirose@gmail.com>
Subject: [PATCH net-next 1/2] vtun: fix typos.
Date: Mon, 26 Nov 2012 10:07:40 +0200 [thread overview]
Message-ID: <1353917261-2974-2-git-send-email-ramirose@gmail.com> (raw)
In-Reply-To: <1353917261-2974-1-git-send-email-ramirose@gmail.com>
This patch fixes four typos in drivers/net/vtun.c.
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
drivers/net/tun.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/tun.c b/drivers/net/tun.c
index 3bd9932..1dfb135 100644
--- a/drivers/net/tun.c
+++ b/drivers/net/tun.c
@@ -121,11 +121,11 @@ struct tap_filter {
* also contains all socket related strctures (except sock_fprog and tap_filter)
* to serve as one transmit queue for tuntap device. The sock_fprog and
* tap_filter were kept in tun_struct since they were used for filtering for the
- * netdevice not for a specific queue (at least I didn't see the reqirement for
+ * netdevice not for a specific queue (at least I didn't see the requirement for
* this).
*
* RCU usage:
- * The tun_file and tun_struct are loosely coupled, the pointer from on to the
+ * The tun_file and tun_struct are loosely coupled, the pointer from one to the
* other can only be read while rcu_read_lock or rtnl_lock is held.
*/
struct tun_file {
@@ -153,7 +153,7 @@ struct tun_flow_entry {
#define TUN_NUM_FLOW_ENTRIES 1024
/* Since the socket were moved to tun_file, to preserve the behavior of persist
- * device, socket fileter, sndbuf and vnet header size were restore when the
+ * device, socket filter, sndbuf and vnet header size were restore when the
* file were attached to a persist device.
*/
struct tun_struct {
@@ -689,7 +689,7 @@ static netdev_tx_t tun_net_xmit(struct sk_buff *skb, struct net_device *dev)
sk_filter(tfile->socket.sk, skb))
goto drop;
- /* Limit the number of packets queued by divining txq length with the
+ /* Limit the number of packets queued by dividing txq length with the
* number of queues.
*/
if (skb_queue_len(&tfile->socket.sk->sk_receive_queue)
--
1.7.11.7
next prev parent reply other threads:[~2012-11-26 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 8:07 [PATCH net-next 0/2] tun: trivial fixes Rami Rosen
2012-11-26 8:07 ` Rami Rosen [this message]
2012-11-26 8:07 ` [PATCH net-next 2/2] tun: put correct method name in a debug message Rami Rosen
2012-11-26 22:31 ` Joe Perches
2012-11-26 22:22 ` [PATCH net-next 0/2] tun: trivial fixes David Miller
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=1353917261-2974-2-git-send-email-ramirose@gmail.com \
--to=ramirose@gmail.com \
--cc=davem@davemloft.net \
--cc=maxk@qti.qualcomm.com \
--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).