From: Steffen Klassert <steffen.klassert@secunet.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: <linux-crypto@vger.kernel.org>, <dan.carpenter@oracle.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] padata: get_next is never NULL
Date: Fri, 14 Apr 2017 09:46:43 +0200 [thread overview]
Message-ID: <20170414074643.GH12763@secunet.com> (raw)
In-Reply-To: <20170412084019.16190-1-Jason@zx2c4.com>
On Wed, Apr 12, 2017 at 10:40:19AM +0200, Jason A. Donenfeld wrote:
> Per Dan's static checker warning, the code that returns NULL was removed
> in 2010, so this patch updates the comments and fixes the code
> assumptions.
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
This looks ok,
Acked-by: Steffen Klassert <steffen.klassert@secunet.com>
prev parent reply other threads:[~2017-04-14 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 9:16 [bug report] padata: simplify serialization mechanism Dan Carpenter
2017-04-12 8:40 ` [PATCH] padata: get_next is never NULL Jason A. Donenfeld
2017-04-14 7:46 ` Steffen Klassert [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=20170414074643.GH12763@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=Jason@zx2c4.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).