From: John Levon <levon@movementarian.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: smatch@vger.kernel.org
Subject: Re: Odd smatch issue?
Date: Mon, 14 Jan 2019 14:47:36 +0000 [thread overview]
Message-ID: <20190114144736.GA14913@movementarian.org> (raw)
In-Reply-To: <20190114143800.GF4504@kadam>
On Mon, Jan 14, 2019 at 05:38:00PM +0300, Dan Carpenter wrote:
> Try this patch?
With both applied, smatch now catches the bad code, thanks!
Time to run it across everything...
regards
john
next prev parent reply other threads:[~2019-01-14 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 12:32 Odd smatch issue? John Levon
2019-01-14 10:18 ` Dan Carpenter
2019-01-14 12:42 ` John Levon
2019-01-14 14:38 ` Dan Carpenter
2019-01-14 14:47 ` John Levon [this message]
2019-01-14 14:51 ` Dan Carpenter
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=20190114144736.GA14913@movementarian.org \
--to=levon@movementarian.org \
--cc=dan.carpenter@oracle.com \
--cc=smatch@vger.kernel.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.