From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001949] ConfigTool - Patch to resolve 'set but usused' variable warnings
Date: Sun, 02 Mar 2014 16:45:00 -0000 [thread overview]
Message-ID: <bug-1001949-104-nNdJzt7he5@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001949-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001949
Andy Jackson <andy@xylanta.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #2460|0 |1
is obsolete| |
--- Comment #2 from Andy Jackson <andy@xylanta.com> ---
Created attachment 2476
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2476&action=edit
Revised patch to resolve 'set but usused' variable warnings
Updated patch which uses CYG_UNUSED_PARAM
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-03-02 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 15:51 [Bug 1001949] New: " bugzilla-daemon
2014-02-28 10:24 ` [Bug 1001949] " bugzilla-daemon
2014-03-02 16:45 ` bugzilla-daemon [this message]
2014-03-13 15:05 ` 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-1001949-104-nNdJzt7he5@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--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).