From: Andrew Lunn <andrew@lunn.ch>
To: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] [PATCH] fix possible jffs2 deadlock (sync with mtd cvs)
Date: Mon, 02 Aug 2004 14:08:00 -0000 [thread overview]
Message-ID: <20040802140819.GL14248@lunn.ch> (raw)
In-Reply-To: <5A8A17126B73AC4C83968F6C4505E3C5EA64A3@JO-EX01.JENOPTIK.NET>
On Mon, Aug 02, 2004 at 03:09:51PM +0200, Neundorf, Alexander wrote:
>
> ...
> > > Ok, I'll have a look.
> > > What about the patch ?
> >
> > It was decided by the jffs2 maintainer to reject the patch. Its the
> > compiler that is broken, not JFFS2. Fixing the compiler is the proper
> > solution.
> >
> > Andrew
>
> No, not that patch. I mean the patch which is attached to my
> previous mail, which fixes the semaphore-unlocking problem (and
> which is taken from mtd cvs HEAD). This is unrelated to the arm-gcc
> problem.
Sorry, my mistake.
I want to resync the eCos jffs2 code with dwnw2 repository which will
automatically pull in your patch. But its not as simple as that
becasue the last time this was done an eCos change was overwritten so
that needs putting back and then committing to the dwnw2 repository,
plus i have some other local changes in my tree for the reworked flash
API which should not be committed....
This will happen, but not today.
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:[~2004-08-02 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 13:09 AW: " Neundorf, Alexander
2004-08-02 14:08 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-02 12:55 Neundorf, Alexander
2004-08-02 13:03 ` Andrew Lunn
2004-07-30 10:41 Neundorf, Alexander
2004-08-02 11:12 ` Andrew Lunn
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=20040802140819.GL14248@lunn.ch \
--to=andrew@lunn.ch \
--cc=Alexander.Neundorf@jenoptik.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).