Mercurial > hg > freeDiameter
changeset 1099:6ce5c99a40af
Fix some typos.
| author | Thomas Klausner <tk@giga.or.at> |
|---|---|
| date | Wed, 08 May 2013 14:40:20 +0200 |
| parents | 4d2dcb54d9a6 |
| children | 4b7192d0ffde |
| files | include/freeDiameter/libfdcore.h libfdcore/cnxctx.c libfdcore/p_sr.c libfdproto/messages.c |
| diffstat | 4 files changed, 7 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/include/freeDiameter/libfdcore.h Mon May 06 18:49:59 2013 +0800 +++ b/include/freeDiameter/libfdcore.h Wed May 08 14:40:20 2013 +0200 @@ -952,7 +952,7 @@ */ HOOK_MESSAGE_FAILOVER, - /* Hook called when a message that was sent to a peer is being requeued, because e.g. the connection was teared down. + /* Hook called when a message that was sent to a peer is being requeued, because e.g. the connection was torn down. In that case the message will go again through the routing process. - {msg} points to the corresponding request message (the answer is discarded). Again, the objects may not have been dictionary resolved. If you try to call fd_msg_parse_dict, it might slow down the operation of a relay agent, although this hook is not on the normal execution path. @@ -1021,7 +1021,7 @@ }; -/* Type if the {permsgdata} ointer. It is up to each extension to define its own structure. This is opaque for the framework. */ +/* Type of the {permsgdata} pointer. It is up to each extension to define its own structure. This is opaque for the framework. */ struct fd_hook_permsgdata; /* A handle that will be associated with the extension, and with the permsgdata structures. */ @@ -1034,7 +1034,7 @@ * FUNCTION: fd_hook_data_register * * PARAMETERS: - * permsgdata_new_cb : function called to initialize a new empty fd_hook_permsgdata structure, when a hook will be called for a message with not structure yet. If the function returns NULL, it will be called again for the next hook. + * permsgdata_new_cb : function called to initialize a new empty fd_hook_permsgdata structure, when a hook will be called for a message with no structure yet. If the function returns NULL, it will be called again for the next hook. * permsgdata_destroy_cb : function called when a message is being disposed. It should free the resources associated with the fd_hook_permsgdata. * new_handle : On success, a handler to the registered callback is stored here. * This handler will be used to unregister the cb.
--- a/libfdcore/cnxctx.c Mon May 06 18:49:59 2013 +0800 +++ b/libfdcore/cnxctx.c Wed May 08 14:40:20 2013 +0200 @@ -1755,7 +1755,7 @@ #endif /* DISABLE_SCTP */ default: - TRACE_DEBUG(INFO, "Unknwon protocol: %d", conn->cc_proto); + TRACE_DEBUG(INFO, "Unknown protocol: %d", conn->cc_proto); ASSERT(0); return ENOTSUP; /* or EINVAL... */ }
--- a/libfdcore/p_sr.c Mon May 06 18:49:59 2013 +0800 +++ b/libfdcore/p_sr.c Wed May 08 14:40:20 2013 +0200 @@ -195,7 +195,7 @@ /* loop */ } while (1); error: - ; /* pthread_cleanup_pop sometimes expands as "} ..." and the label beofre this cause some compilers to complain... */ + ; /* pthread_cleanup_pop sometimes expands as "} ..." and the label before this cause some compilers to complain... */ pthread_cleanup_pop( 1 ); ASSERT(0); /* we have encountered a problem, maybe time to signal the framework to terminate? */ return NULL;
--- a/libfdproto/messages.c Mon May 06 18:49:59 2013 +0800 +++ b/libfdproto/messages.c Wed May 08 14:40:20 2013 +0200 @@ -1250,8 +1250,8 @@ if (! (msg->msg_public.msg_flags & CMD_FLAG_REQUEST )) return anscb ? EINVAL : 0; /* we associate with requests only */ - CHECK_PARAMS( (anscb == NULL) || (msg->msg_cb.anscb == NULL) ); /* We are not overwritting a cb */ - CHECK_PARAMS( (expirecb == NULL) || (msg->msg_cb.expirecb == NULL) ); /* We are not overwritting a cb */ + CHECK_PARAMS( (anscb == NULL) || (msg->msg_cb.anscb == NULL) ); /* We are not overwriting a cb */ + CHECK_PARAMS( (expirecb == NULL) || (msg->msg_cb.expirecb == NULL) ); /* We are not overwriting a cb */ /* Associate callback and data with the message, if any */ msg->msg_cb.anscb = anscb;