From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: eCos Disuss <ecos-patches@ecos.sourceware.org>
Subject: Bugfix for romfs
Date: Fri, 03 Jul 2009 12:45:00 -0000 [thread overview]
Message-ID: <c09652430907030545x61d49f02te319fd92c2dd891e@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
2009-04-28 Øyvind Harboe <oyvind.harboe@zylin.com>
* src/romfs.c: file name comparsion was broken for two files
with the same stem. A directory/file called "foo" would not
be found if there was a file "foo*" before "foo".
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
[-- Attachment #2: fixromfs.txt --]
[-- Type: text/plain, Size: 1154 bytes --]
Index: current/ChangeLog
===================================================================
RCS file: /cvs/ecos/ecos/packages/fs/rom/current/ChangeLog,v
retrieving revision 1.27
diff -u -w -r1.27 ChangeLog
--- current/ChangeLog 28 Apr 2009 13:06:11 -0000 1.27
+++ current/ChangeLog 3 Jul 2009 12:44:06 -0000
@@ -1,3 +1,9 @@
+2009-04-28 Øyvind Harboe <oyvind.harboe@zylin.com>
+
+ * src/romfs.c: file name comparsion was broken for two files
+ with the same stem. A directory/filed called "foo" would not
+ be found if there was a file "foo*" before "foo".
+
2009-04-28 John Dallaway <john@dallaway.org.uk>
cdl/romfs.cdl: Use CYGPKG_IO_FILEIO as the parent.
Index: current/src/romfs.c
===================================================================
RCS file: /cvs/ecos/ecos/packages/fs/rom/current/src/romfs.c,v
retrieving revision 1.10
diff -u -w -r1.10 romfs.c
--- current/src/romfs.c 29 Jan 2009 17:48:54 -0000 1.10
+++ current/src/romfs.c 3 Jul 2009 12:44:07 -0000
@@ -336,7 +336,7 @@
{
for ( ; len > 0 && *a && *b && *a == *b ; a++, b++, len-- )
;
- return ( len == 0 );
+ return ( len == 0 ) && (*a==0);
}
reply other threads:[~2009-07-03 12:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c09652430907030545x61d49f02te319fd92c2dd891e@mail.gmail.com \
--to=oyvind.harboe@zylin.com \
--cc=ecos-patches@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).