public inbox for b.a.t.m.a.n@lists.open-mesh.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 next] batman-adv: fix typ0s in comment and kerneldoc
Date: Sat, 19 Oct 2013 17:04:14 +0200	[thread overview]
Message-ID: <1382195054-1943-1-git-send-email-antonio@meshcoding.com> (raw)

Introduced by 21a57f6e7a3b4455dfe68ee07a7b901d9e7f200b
("batman-adv: make the TT CRC logic VLAN specific")

Signed-off-by: Antonio Quartulli <antonio@meshcoding.com>
---
 translation-table.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/translation-table.c b/translation-table.c
index 5750c88..4add57d 100644
--- a/translation-table.c
+++ b/translation-table.c
@@ -2181,7 +2181,7 @@ static int batadv_tt_global_valid(const void *entry_ptr,
 }
 
 /**
- * batadv_tt_tvlv_generate - fill the tvlv buff it with the tt entries from the
+ * batadv_tt_tvlv_generate - fill the tvlv buff with the tt entries from the
  *  specified tt hash
  * @bat_priv: the bat priv with all the soft interface information
  * @hash: hash table containing the tt entries
@@ -2359,7 +2359,7 @@ static int batadv_send_tt_request(struct batadv_priv *bat_priv,
 	tvlv_tt_data->num_vlan = htons(num_vlan);
 
 	/* send all the CRCs within the request. This is needed by intermediate
-	 * node to ensure they have the correct table before replying
+	 * nodes to ensure they have the correct table before replying
 	 */
 	tt_vlan_req = (struct batadv_tvlv_tt_vlan_data *)(tvlv_tt_data + 1);
 	for (i = 0; i < num_vlan; i++) {
-- 
1.8.4


             reply	other threads:[~2013-10-19 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 15:04 Antonio Quartulli [this message]
2013-10-19 20:22 ` [B.A.T.M.A.N.] [PATCH next] batman-adv: fix typ0s in comment and kerneldoc 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=1382195054-1943-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox