[PATCH] Fix comments for object lookup err. -> status map

Joel Sherrill joel at rtems.org
Tue Nov 21 18:40:57 UTC 2017


Pushed. Thanks.

On Mon, Nov 20, 2017 at 11:53 AM, Martin Erik Werner <
martinerikwerner.aac at gmail.com> wrote:

> Based on correlation with the enum for object lookup errors in
> cpukit/score/include/rtems/score/objectimpl.h:
>
> typedef enum {
>  OBJECTS_NAME_OR_ID_LOOKUP_SUCCESSFUL,
>  OBJECTS_INVALID_NAME,
>  OBJECTS_INVALID_ADDRESS,
>  OBJECTS_INVALID_ID,
>  OBJECTS_INVALID_NODE
> } Objects_Name_or_id_lookup_errors;
>
> update the comments regarding the object lookup error to status map to
> match.
>
> Signed-off-by: Martin Erik Werner <martin.werner at aacmicrotec.com>
> ---
>  cpukit/rtems/src/status.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/cpukit/rtems/src/status.c b/cpukit/rtems/src/status.c
> index 810c0e18de..3eadea59f0 100644
> --- a/cpukit/rtems/src/status.c
> +++ b/cpukit/rtems/src/status.c
> @@ -17,13 +17,13 @@
>  #include <errno.h>
>
>  const rtems_status_code _Status_Object_name_errors_to_status[] = {
> -  /** This maps OBJECTS_SUCCESSFUL to RTEMS_SUCCESSFUL. */
> +  /** This maps OBJECTS_NAME_OR_ID_LOOKUP_SUCCESSFUL to
> RTEMS_SUCCESSFUL. */
>    RTEMS_SUCCESSFUL,
>    /** This maps OBJECTS_INVALID_NAME to RTEMS_INVALID_NAME. */
>    RTEMS_INVALID_NAME,
> -  /** This maps OBJECTS_INVALID_ADDRESS to RTEMS_INVALID_NAME. */
> +  /** This maps OBJECTS_INVALID_ADDRESS to RTEMS_INVALID_ADDRESS. */
>    RTEMS_INVALID_ADDRESS,
> -  /** This maps OBJECTS_INVALID_ID to RTEMS_INVALID_ADDRESS. */
> +  /** This maps OBJECTS_INVALID_ID to RTEMS_INVALID_ID. */
>    RTEMS_INVALID_ID,
>    /** This maps OBJECTS_INVALID_NODE to RTEMS_INVALID_NODE. */
>    RTEMS_INVALID_NODE
> --
> 2.11.0
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20171121/5dc861aa/attachment-0002.html>


More information about the devel mailing list