From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-trivial@nongnu.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] libcacard/cac: Remove unused statement (value stored is never read)
Date: Mon, 02 Dec 2013 21:07:20 +0400 [thread overview]
Message-ID: <529CBE48.8060801@msgid.tls.msk.ru> (raw)
In-Reply-To: <1384722683-17205-1-git-send-email-sw@weilnetz.de>
18.11.2013 01:11, Stefan Weil wrote:
> Warning from ccc-analyzer:
>
> libcacard/cac.c:192:13: warning: Value stored to 'ret' is never read
> ret = VCARD_DONE;
> ^ ~~~~~~~~~~
>
> Here 'ret' is assigned a value inside of a switch statement and also after
> that switch statement.
Applied to trivial patches, thank you!
/mjt
prev parent reply other threads:[~2013-12-02 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 21:11 [Qemu-devel] [PATCH] libcacard/cac: Remove unused statement (value stored is never read) Stefan Weil
2013-12-02 17:07 ` Michael Tokarev [this message]
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=529CBE48.8060801@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/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 NNTP newsgroup(s).