From: Andrew Parlane <andrewp@carallon.com>
To: Nick Garnett <nickg@calivar.com>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Spurious interrupt on ARM.
Date: Fri, 01 Nov 2013 17:54:00 -0000 [thread overview]
Message-ID: <5273EAD3.3020606@carallon.com> (raw)
In-Reply-To: <5273E9FB.40505@calivar.com>
Ah, ok.
I already fixed it locally, I just wanted to make sure I wasn't missing
something and also make others aware of the issue.
Thanks,
Andrew
On 01/11/2013 17:50, Nick Garnett wrote:
>
> On 01/11/13 17:46, Andrew Parlane wrote:
>> Excellent thanks. I guess we're a bit out of date.
> Not really. I have an internal change here that is not in the public
> sources. I'll take a look at pushing it out to the public repository. In
> the meantime you can just update your sources locally.
>
>
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2013-11-01 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 17:15 Andrew Parlane
2013-11-01 17:06 ` Nick Garnett
2013-11-01 17:20 ` Andrew Parlane
2013-11-01 17:42 ` Nick Garnett
2013-11-01 17:46 ` Andrew Parlane
2013-11-01 17:50 ` Nick Garnett
2013-11-01 17:54 ` Andrew Parlane [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=5273EAD3.3020606@carallon.com \
--to=andrewp@carallon.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=nickg@calivar.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).