All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <antonio@meshcoding.com>
Subject: [B.A.T.M.A.N.] [PATCH] batman-adv: fix typ0 in kerneldoc and comment
Date: Wed, 14 May 2014 14:23:15 +0200	[thread overview]
Message-ID: <1400070195-26148-1-git-send-email-antonio@meshcoding.com> (raw)

Introduced by 9b9cdbe28e2b9c8bdf9c761f22ba9655963d13d4
("batman-adv: fix removing neigh_ifinfo")

Signed-off-by: Antonio Quartulli <antonio@meshcoding.com>
Reported-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
 originator.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/originator.c b/originator.c
index 9ebc40e..abf612d 100644
--- a/originator.c
+++ b/originator.c
@@ -704,7 +704,7 @@ free_orig_node:
 /**
  * batadv_purge_neigh_ifinfo - purge obsolete ifinfo entries from neighbor
  * @bat_priv: the bat priv with all the soft interface information
- * @neigh_node: orig node which is to be checked
+ * @neigh: orig node which is to be checked
  */
 static void
 batadv_purge_neigh_ifinfo(struct batadv_priv *bat_priv,
@@ -842,7 +842,7 @@ batadv_purge_orig_neighbors(struct batadv_priv *bat_priv,
 			hlist_del_rcu(&neigh_node->list);
 			batadv_neigh_node_free_ref(neigh_node);
 		} else {
-			/* only neccesary if not the whole neighbor is to be
+			/* only necessary if not the whole neighbor is to be
 			 * deleted, but some interface has been removed.
 			 */
 			batadv_purge_neigh_ifinfo(bat_priv, neigh_node);
-- 
1.8.5.5


             reply	other threads:[~2014-05-14 12:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 12:23 Antonio Quartulli [this message]
2014-05-14 21:15 ` [B.A.T.M.A.N.] [PATCH] batman-adv: fix typ0 in kerneldoc and comment Marek Lindner

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=1400070195-26148-1-git-send-email-antonio@meshcoding.com \
    --to=antonio@meshcoding.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.