From: Dan Carpenter <dan.carpenter@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Unreachable code diagnostic
Date: Fri, 24 Feb 2017 22:26:53 +0300 [thread overview]
Message-ID: <20170224192653.GA4480@mwanda> (raw)
In-Reply-To: <20170224180759.GB16328@bombadil.infradead.org>
Smatch works pretty well for finding unreachable code.
regards,
dan carpenter
prev parent reply other threads:[~2017-02-24 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 18:07 Unreachable code diagnostic Matthew Wilcox
2017-02-24 18:33 ` Linus Torvalds
2017-02-24 20:11 ` Luc Van Oostenryck
2017-02-24 20:43 ` Josh Triplett
2017-02-24 20:47 ` Luc Van Oostenryck
2017-02-24 18:57 ` Josh Triplett
2017-02-24 19:56 ` Luc Van Oostenryck
2017-02-24 21:05 ` Matthew Wilcox
2017-02-24 19:26 ` Dan Carpenter [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=20170224192653.GA4480@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-sparse@vger.kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.