gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] r30296 - gnunet/src/mesh


From: gnunet
Subject: [GNUnet-SVN] r30296 - gnunet/src/mesh
Date: Fri, 18 Oct 2013 13:34:19 +0200

Author: bartpolot
Date: 2013-10-18 13:34:19 +0200 (Fri, 18 Oct 2013)
New Revision: 30296

Modified:
   gnunet/src/mesh/gnunet-service-mesh_peer.c
   gnunet/src/mesh/gnunet-service-mesh_peer.h
Log:
- doxygen

Modified: gnunet/src/mesh/gnunet-service-mesh_peer.c
===================================================================
--- gnunet/src/mesh/gnunet-service-mesh_peer.c  2013-10-18 11:32:23 UTC (rev 
30295)
+++ gnunet/src/mesh/gnunet-service-mesh_peer.c  2013-10-18 11:34:19 UTC (rev 
30296)
@@ -553,7 +553,7 @@
 /**
  * Returns if peer is used (has a tunnel, is neighbor).
  *
- * @peer Peer to check.
+ * @param peer Peer to check.
  *
  * @return GNUNET_YES if peer is in use.
  */
@@ -1226,7 +1226,7 @@
  * Retrieve the MeshPeer stucture associated with the peer, create one
  * and insert it in the appropriate structures if the peer is not known yet.
  *
- * @param peer Full identity of the peer.
+ * @param peer_id Full identity of the peer.
  *
  * @return Existing or newly created peer structure.
  */
@@ -1522,7 +1522,7 @@
  * The path is given in peer_info -> destination, therefore we turn the path
  * upside down first.
  *
- * @param peer_info Peer to add the path to, being the origin of the path.
+ * @param pee 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?

Modified: gnunet/src/mesh/gnunet-service-mesh_peer.h
===================================================================
--- gnunet/src/mesh/gnunet-service-mesh_peer.h  2013-10-18 11:32:23 UTC (rev 
30295)
+++ gnunet/src/mesh/gnunet-service-mesh_peer.h  2013-10-18 11:34:19 UTC (rev 
30296)
@@ -85,7 +85,7 @@
  * Retrieve the MeshPeer stucture associated with the peer, create one
  * and insert it in the appropriate structures if the peer is not known yet.
  *
- * @param peer Full identity of the peer.
+ * @param peer_id Full identity of the peer.
  *
  * @return Existing or newly created peer structure.
  */
@@ -207,7 +207,7 @@
  * The path is given in peer_info -> destination, therefore we turn the path
  * upside down first.
  *
- * @param peer_info 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?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]