From: Andrew Lunn <andrew@lunn.ch>
To: "Doyle, Patrick" <WPD@dtccom.com>
Cc: "'ecos-discuss@ecos.sourceware.org'" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] JFFS2 on ARM target
Date: Thu, 09 Mar 2006 20:39:00 -0000 [thread overview]
Message-ID: <20060309203858.GI19406@lunn.ch> (raw)
In-Reply-To: <3EDBCCE80E95E744A99895CA464987C4A7D295@dtcsrvr09>
On Thu, Mar 09, 2006 at 03:19:08PM -0500, Doyle, Patrick wrote:
> Hello again Andrew,
>
> OK, I've poked around a bit...
>
> What I've seen is that the jffs2 tree has migrated a bit since it was
> imported into the eCos tree. The other thing I've seen is an "ecos"
> directory which has your fingerprints all over it :-)
Yes, but not for a while. As you said, the jffs2 tree has moved on
quite a lot. I've no idea if it will compile inside eCos any more.
> I'm not in a position right now to upgrade eCos to the latest jffs2, so what
> I would like to do is to submit ?yvind's patch (suitably updated to reflect
> the latest changes in jffs2) to the jffs2 maintainer while simultaneously
> submitting the same patch (suitably not updated) for integration into eCos.
I expect it will be reject. It was when Oyvind submitted the
patch. There response was something like: Gcc is broken, fix gcc.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-03-09 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 20:11 Doyle, Patrick
2006-03-09 20:39 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-09 16:18 Doyle, Patrick
2006-03-09 20:42 ` Andrew Lunn
2006-06-20 14:35 ` Jürgen Lambrecht
2006-03-08 20:00 Doyle, Patrick
2006-03-08 21:58 ` Andrew Lunn
2006-03-08 23:03 ` Newsgroups Reader
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=20060309203858.GI19406@lunn.ch \
--to=andrew@lunn.ch \
--cc=WPD@dtccom.com \
--cc=ecos-discuss@ecos.sourceware.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 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).