public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/2] lib/alchemy: change API context tags
Date: Mon, 17 Jul 2017 16:39:42 +0200	[thread overview]
Message-ID: <20170717163942.6f4ebab9@md1em3qc> (raw)
In-Reply-To: <20170717143822.11844-3-henning.schild@siemens.com>

Sorry those two where still setting in a tmp-folder. Not for Isar.

Henning

Am Mon, 17 Jul 2017 16:38:22 +0200
schrieb Henning Schild <henning.schild@siemens.com>:

> From: Henning Schild <henning.schild@siemens.com>
> 
> changing the prio always changes the secondary-mode thread as well
> see:
>   http://xenomai.org/migrating-from-xenomai-2-x-to-3-x/#Scheduling
> 
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
>  lib/alchemy/task.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/alchemy/task.c b/lib/alchemy/task.c
> index d647d5c0ee..12acafc495 100644
> --- a/lib/alchemy/task.c
> +++ b/lib/alchemy/task.c
> @@ -1243,7 +1243,7 @@ RT_TASK *rt_task_self(void)
>   * - -EPERM is returned if @a task is NULL and this service was
> called
>   * from an invalid context.
>   *
> - * @apitags{mode-unrestricted, switch-primary}
> + * @apitags{mode-unrestricted, switch-primary, switch-secondary}
>   *
>   * @note The caller must be an Alchemy task if @a task is NULL.
>   *


      reply	other threads:[~2017-07-17 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 14:38 [PATCH 1/2] lib/alchemy: fix rt_mutex_create return values Henning Schild
2017-07-17 14:38 ` [PATCH] meta: dpkg: remove redundant 'addtask' Henning Schild
2017-07-22 22:11   ` Baurzhan Ismagulov
2017-07-17 14:38 ` [PATCH 2/2] lib/alchemy: change API context tags Henning Schild
2017-07-17 14:39   ` Henning Schild [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170717163942.6f4ebab9@md1em3qc \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox