From: Michael Welling <mwelling@ieee.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: mwelling79@gmail.com, Jan Kiszka <jan.kiszka@siemens.com>,
xenomai@xenomai.org
Subject: Re: [Xenomai] RT serial cross-link failure
Date: Mon, 22 Feb 2016 15:29:44 -0600 [thread overview]
Message-ID: <20160222212944.GA14055@deathstar> (raw)
In-Reply-To: <20160222211439.GH7398@hermes.click-hack.org>
On Mon, Feb 22, 2016 at 10:14:39PM +0100, Gilles Chanteperdrix wrote:
> > > > Why in the world would -ETIMEDOUT come out as Operation not permitted?
> > >
> > > Because EPERM is -1. ioctl return -1 upon error and the "real" error
> > > status is found in errno. So, in fact, the test should check errno
> > > if err is not 0.
> >
> > Ah I see it now. Would you like a patch for the cross-link demo?
>
> Yes, thanks.
Sent.
Would you like a properly formed patch for the imx uart driver?
>
> --
> Gilles.
> https://click-hack.org
prev parent reply other threads:[~2016-02-22 21:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 17:41 [Xenomai] RT serial cross-link failure Michael Welling
2016-02-16 5:39 ` Wolfgang Netbal
2016-02-16 17:25 ` Michael Welling
2016-02-16 17:29 ` Gilles Chanteperdrix
2016-02-16 17:36 ` Michael Welling
2016-02-16 17:58 ` Michael Welling
2016-02-18 7:02 ` Wolfgang Netbal
2016-02-18 7:10 ` Michael Welling
2016-02-18 7:30 ` Wolfgang Netbal
2016-02-18 16:10 ` Michael Welling
2016-02-22 17:53 ` Michael Welling
2016-02-22 18:05 ` Jan Kiszka
2016-02-22 19:04 ` Michael Welling
2016-02-22 19:16 ` Jan Kiszka
2016-02-22 19:22 ` Gilles Chanteperdrix
2016-02-22 19:46 ` Michael Welling
2016-02-22 20:34 ` Gilles Chanteperdrix
2016-02-22 20:51 ` Michael Welling
2016-02-22 21:02 ` Gilles Chanteperdrix
2016-02-22 21:10 ` Michael Welling
2016-02-22 21:14 ` Gilles Chanteperdrix
2016-02-22 21:29 ` Michael Welling [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=20160222212944.GA14055@deathstar \
--to=mwelling@ieee.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=mwelling79@gmail.com \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.