From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Michael Bergandi <mbergandi@gmail.com>
Cc: eCos Developer List <ecos-devel@ecos.sourceware.org>
Subject: Re: cyg_drv_dsr_lock usage
Date: Tue, 11 Oct 2011 19:42:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1110112214040.7883@vostro> (raw)
In-Reply-To: <CAOHvnTPvK=cHb9s1iABjOkyyXzxyBLdmrCc=z5GzkOfDV9g67A@mail.gmail.com>
On Thu, 6 Oct 2011, Michael Bergandi wrote:
> Anyone?
[story entirely]
http://ecos.sourceware.org/ml/ecos-devel/2011-09/msg00003.html
That's what I+Google found. There was one expert explanation by the
topic in the ecos-discuss list
http://ecos.sourceware.org/ml/ecos-discuss/2003-03/msg00178.html
It seems to me that in some cases you would get more help (=hands)
through the eCos discuss list and ... search engines :-)
Thus, I found/saw no issues with in the posted snippet of the code.
Sergei
prev parent reply other threads:[~2011-10-11 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 0:43 Michael Bergandi
2011-10-06 16:53 ` Michael Bergandi
2011-10-11 19:42 ` Sergei Gavrikov [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=alpine.DEB.2.00.1110112214040.7883@vostro \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=mbergandi@gmail.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).