From: Mark Salter <msalter@redhat.com>
To: jifl@eCosCentric.com
Cc: andrew@lunn.ch, ecos-maintainers@sources.redhat.com,
ecos-patches@sources.redhat.com
Subject: Re: ARM HAL exception handling
Date: Wed, 15 Oct 2003 13:39:00 -0000 [thread overview]
Message-ID: <20031015133821.EF2F878B9C@deneb.localdomain> (raw)
In-Reply-To: <3F8C80E0.1010808@eCosCentric.com> (message from Jonathan Larmour on Wed, 15 Oct 2003 00:04:00 +0100)
>>>>> Jonathan Larmour writes:
> Andrew Lunn wrote:
>> Hi folks
>>
>> I don't know enough about thumb to deal with this patch. Please can
>> someone else take a look.
> Mark's the expert on this stuff AFAIK, but firstly it mostly only affects
> #ifdef CYGHWR_HAL_ARM_DUMP_EXCEPTIONS stuff, so can't be too problematic.
> Clearly the current stuff doesn't grok thumb at all. The change looks
> reasonable.
Yes, I agree. The changes look right to me.
--Mark
prev parent reply other threads:[~2003-10-15 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200310131818.30676.thomas.koeller@baslerweb.com>
2003-10-14 7:22 ` Andrew Lunn
2003-10-14 23:04 ` Jonathan Larmour
2003-10-15 13:39 ` Mark Salter [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=20031015133821.EF2F878B9C@deneb.localdomain \
--to=msalter@redhat.com \
--cc=andrew@lunn.ch \
--cc=ecos-maintainers@sources.redhat.com \
--cc=ecos-patches@sources.redhat.com \
--cc=jifl@eCosCentric.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).