From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: Ingo Schwarze <schwarze@usta.de>
Cc: tech@mdocml.bsd.lv
Subject: Re: [patch] remove dead code
Date: Sat, 18 May 2013 21:21:29 +0200 [thread overview]
Message-ID: <20130518192129.GG2055@acme.spoerlein.net> (raw)
In-Reply-To: <20130518171207.GA13985@iris.usta.de>
On Sat, 2013-05-18 at 19:12:07 +0200, Ingo Schwarze wrote:
> Hi Ulrich,
>
> Ulrich Spörlein wrote on Fri, May 17, 2013 at 03:00:50AM +0200:
>
> > please see the following patch which removes a bit of dead code.
> > With sz being invariant 0, the loop will never do anything.
>
> Right, committed to both bsd.lv and openbsd.org.
>
> > This is Coverity Scan CID 975717
>
> Strangly enough, it seems that Coverity missed that **params is
> unused as well. Anyway, i removed **params, too.
It only reports dead "code", not unused vars :)
Cheers,
Uli
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2013-05-18 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 1:00 Ulrich Spörlein
2013-05-18 17:12 ` Ingo Schwarze
2013-05-18 19:21 ` Ulrich Spörlein [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=20130518192129.GG2055@acme.spoerlein.net \
--to=uqs@spoerlein.net \
--cc=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
/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).