From: David Howells <dhowells@redhat.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] KEYS: remove a bogus NULL check
Date: Mon, 24 Nov 2014 13:42:23 +0000 [thread overview]
Message-ID: <16495.1416836543@warthog.procyon.org.uk> (raw)
In-Reply-To: <20141122184201.GE6994@mwanda>
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> We already checked if "desc" was NULL at the beginning of the function
> and we've dereferenced it so this causes a static checker warning.
Yeah - keys were originally allowed to have no description.
Applied.
prev parent reply other threads:[~2014-11-24 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 18:42 [patch] KEYS: remove a bogus NULL check Dan Carpenter
2014-11-24 13:42 ` 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=16495.1416836543@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