public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001641] New: Erase function in flashiodev.c and flashiodevlegacy.c handle "err_address" differently
Date: Wed, 01 Aug 2012 09:11:00 -0000	[thread overview]
Message-ID: <bug-1001641-13@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001641

           Summary: Erase function in flashiodev.c and flashiodevlegacy.c
                    handle "err_address" differently
           Product: eCos
           Version: CVS
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: low
         Component: Flash
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: bernd.edlinger@hotmail.de
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


Created an attachment (id=1854)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1854)
proposed patch to fix this defect.

In the function flashiodev_get_config(..,CYG_IO_GET_CONFIG_FLASH_ERASE,..)
the meaning of e->err_address is different in flashiodev.c and in
flashiodevlegacy.c:

Either the address where the error was encountered, or an address where the
result should be stored.

IMHO, the implementation in flashiodev.c makes more sense, and
the flashiodevlegacy.c should be changed accordingly.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-08-01  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01  9:11 bugzilla-daemon [this message]
2012-08-20  9:00 ` [Bug 1001641] " bugzilla-daemon
2012-08-01  9:11 [Bug 1001641] New: " bugzilla-daemon

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=bug-1001641-13@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@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).