From: David Howells <dhowells@redhat.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [bug report] rxrpc: Add some additional call tracing
Date: Wed, 12 Oct 2016 14:59:02 +0000 [thread overview]
Message-ID: <7164.1476284342@warthog.procyon.org.uk> (raw)
In-Reply-To: <20161012061011.GH12841@mwanda>
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> It's just zero or NULL always. But if you want you can also ignore the
> static checker warning since it's obviously harmless.
Ah, yes. The trace line used to be before the error check, but now there's a
separate trace line for that.
David
prev parent reply other threads:[~2016-10-12 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 6:10 [bug report] rxrpc: Add some additional call tracing Dan Carpenter
2016-10-12 7:25 ` David Howells
2016-10-12 8:29 ` Dan Carpenter
2016-10-12 14:59 ` David Howells [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=7164.1476284342@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=kernel-janitors@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox