Changeset 6b83300 in mainline for kernel/generic/include/ipc/sysipc_ops.h

Timestamp:

2012-09-27T21:34:11Z (12 years ago)

Author:

Jakub Jermar <jakub@…>

Branches:

lfn, master, serial, ticket/834-toolchain-update, topic/msim-upgrade, topic/simplify-dev-export

Children:

675fcbd

Parents:

6f9c8f6

Message:

Improve terminology.

File:

• kernel/generic/include/ipc/sysipc_ops.h (modified) (2 diffs)

kernel/generic/include/ipc/sysipc_ops.h

@@ -65 +65 @@
  *
  * The request_process(), answer_preprocess() and answer_process() callbacks
- * will be skipped if the call cannot be dispatched to the callee. This may
- * happen when e.g. the request_preprocess() callback fails or the connection to
- * the callee is not functional. The next callback that will be invoked on the
- * call is request_forget().
+ * will be skipped if the call cannot be delivered to the callee. This may
+ * happen when e.g. the request_preprocess() callback fails or the connection
+ * to the callee is not functional. The next callback that will be invoked on
+ * the call is request_forget().
  *
  * The request_process() callback will be skipped if the callee terminates
  * before picking up the request. In this case, the terminating task will
- * cleanup its dispatched calls list and so the next callback invoked on the
- * call will usually be answer_preprocess(). If, in the meantime, the caller
+ * cleanup its incoming calls list and so the next callback invoked on the call
+ * will usually be answer_preprocess(). If, in the meantime, the caller
  * terminates too, it may happen that the call will be forgotten instead of
  * answered, in which case the kernel will invoke the request_forget() and
@@ -79 +79 @@
  * not defined. 
  *
- * The answer_process() callback will be skipped if the caller terminates before
- * picking up the answer. This means that this callback is not suitable for
- * releasing system resources allocated by the preceding callbacks.
+ * The answer_process() callback will be skipped if the caller terminates
+ * before picking up the answer. This means that this callback is not suitable
+ * for releasing system resources allocated by the preceding callbacks.
  *
  * The comments for each callback type describe the specifics of each callback