- doxygen

diff --git a/src/mesh/gnunet-service-mesh_channel.c b/src/mesh/gnunet-service-mesh_channel.c
index d33425489ca591080d318d8d157bc06d39c7f837..fc949786ebab2e4087ff5d4486e4ebea2a75b792 100644 (file)
--- a/src/mesh/gnunet-service-mesh_channel.c
+++ b/src/mesh/gnunet-service-mesh_channel.c
@@ -1518,7 +1518,7 @@ GMCH_handle_data (struct MeshChannel *ch,
 /**
  * Handler for mesh network traffic end-to-end ACKs.
  *
- * @param t Tunnel on which we got this message.
+ * @param ch Channel on which we got this message.
  * @param msg Data message.
  * @param fwd Is this a fwd ACK? (dest->orig)
  */

diff --git a/src/mesh/gnunet-service-mesh_channel.h b/src/mesh/gnunet-service-mesh_channel.h
index 3d41af4a89abb8cbea08e454b295479156a8ca31..aaead6c30af9c4dc7ea71e15486c18299c560c66 100644 (file)
--- a/src/mesh/gnunet-service-mesh_channel.h
+++ b/src/mesh/gnunet-service-mesh_channel.h
@@ -250,7 +250,7 @@ GMCH_handle_data (struct MeshChannel *ch,
 /**
  * Handler for mesh network traffic end-to-end ACKs.
  *
- * @param t Tunnel on which we got this message.
+ * @param ch Channel on which we got this message.
  * @param msg Data message.
  * @param fwd Is this a fwd ACK? (dest->orig)
  */

diff --git a/src/mesh/gnunet-service-mesh_connection.c b/src/mesh/gnunet-service-mesh_connection.c
index 3abaeda0b095a04a0e8e78bde64ffc7b863b16ec..a36c57772125a7eb7b5e4cfb063b8b34d0184dd2 100644 (file)
--- a/src/mesh/gnunet-service-mesh_connection.c
+++ b/src/mesh/gnunet-service-mesh_connection.c
@@ -2009,6 +2009,7 @@ GMC_notify_broken (struct MeshConnection *c,
 
   fwd = peer == get_prev_hop (c);
 
+  send_broken (c, &my_full_id, GMP_get_id (peer), fwd);
   connection_cancel_queues (c, !fwd);
   if (GMC_is_terminal (c, fwd))
   {
@@ -2017,8 +2018,6 @@ GMC_notify_broken (struct MeshConnection *c,
     return;
   }
 
-  send_broken (c, &my_full_id, GMP_get_id (peer), fwd);
-
   /* Connection will have at least one pending message
    * (the one we just scheduled), so no point in checking whether to
    * destroy immediately. */

diff --git a/src/mesh/gnunet-service-mesh_peer.c b/src/mesh/gnunet-service-mesh_peer.c
index fab01ebd313b84f9ad62f455e4a7adb1e4b265dd..6f46796a2217a3be2d71001e0b4354ceb9e1a9da 100644 (file)
--- a/src/mesh/gnunet-service-mesh_peer.c
+++ b/src/mesh/gnunet-service-mesh_peer.c
@@ -1522,7 +1522,7 @@ GMP_add_path (struct MeshPeer *peer_info, struct MeshPeerPath *path,
  * The path is given in peer_info -> destination, therefore we turn the path
  * upside down first.
  *
- * @param pee Peer to add the path to, being the origin of the path.
+ * @param peer Peer to add the path to, being the origin of the path.
  * @param path New path to add after being inversed.
  *             Path will be either used or freed.
  * @param trusted Do we trust that this path is real?

diff --git a/src/mesh/gnunet-service-mesh_peer.h b/src/mesh/gnunet-service-mesh_peer.h
index 0d164cef9334cb4fb19512b4f0c9c275e1f46952..75989c4cedc23f070c20484a2ffe882eb2cfdd35 100644 (file)
--- a/src/mesh/gnunet-service-mesh_peer.h
+++ b/src/mesh/gnunet-service-mesh_peer.h
@@ -213,7 +213,7 @@ GMP_add_path (struct MeshPeer *peer, struct MeshPeerPath *p, int trusted);
  * @param trusted Do we trust that this path is real?
  */
 void
-GMP_add_path_to_origin (struct MeshPeer *peer_info,
+GMP_add_path_to_origin (struct MeshPeer *peer,
                         struct MeshPeerPath *path,
                         int trusted);
 

diff --git a/src/mesh/gnunet-service-mesh_tunnel.c b/src/mesh/gnunet-service-mesh_tunnel.c
index 231eeabebb97d1a2941b24bd6946ba7c020184d4..d0f3df14ba266f653b27b934a4a5567fdf551008 100644 (file)
--- a/src/mesh/gnunet-service-mesh_tunnel.c
+++ b/src/mesh/gnunet-service-mesh_tunnel.c
@@ -1102,7 +1102,7 @@ GMT_get_next_chid (struct MeshTunnel3 *t)
 
 
 /**
- * Send ACK on one or more channels due to buffer in connections..
+ * Send ACK on one or more channels due to buffer in connections.
  *
  * @param t Channel which has some free buffer space.
  * @param fwd Is this for FWD traffic? (ACK goes to root)