public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Potdar Smita <sspotdar@yahoo.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] eCos Thread Constraints
Date: Thu, 01 Feb 2007 20:19:00 -0000	[thread overview]
Message-ID: <20070201201932.GA5224@lunn.ch> (raw)
In-Reply-To: <276612.91501.qm@web36212.mail.mud.yahoo.com>

On Thu, Feb 01, 2007 at 12:16:29PM -0800, Potdar Smita wrote:
> I had a question about eCos.
> Can eCos threads have any constraints(dependencies)

You mean like unix processes have one parent and possible many
children. Everything is arranged as a tree under pid=1?

No, eCos threads, and threads in general, don't have this.

    Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2007-02-01 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 20:16 Potdar Smita
2007-02-01 20:19 ` Andrew Lunn [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=20070201201932.GA5224@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=sspotdar@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).