From: Jonathan Larmour <jlarmour@redhat.com>
To: Gary Thomas <gthomas@cambridge.redhat.com>
Cc: Nathan J Ickes <nickes@MIT.EDU>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] SA11x0 platform port problems
Date: Mon, 26 Feb 2001 12:17:00 -0000 [thread overview]
Message-ID: <3A9AB9E6.40F5987@redhat.com> (raw)
In-Reply-To: <XFMail.20010226105306.gthomas@cambridge.redhat.com>
Gary Thomas wrote:
>
> I hadn't heard about this at all and I'm not convinced it may be a tools
> problem. However, I have recently revamped this setup which removes
> these problems (no more funny pointers, at least for ROM applications).
> I don't know if/when these changes will hit anon CVS though, so if you
> need them right away, I might be able to provide them to you in private
> email.
Anon CVS should be updated later today probably.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
prev parent reply other threads:[~2001-02-26 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 9:10 Nathan J Ickes
2001-02-26 9:53 ` Gary Thomas
2001-02-26 12:17 ` Jonathan Larmour [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=3A9AB9E6.40F5987@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gthomas@cambridge.redhat.com \
--cc=nickes@MIT.EDU \
/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).