From: Randy Dunlap <rdunlap@xenotime.net>
To: Mark Allyn <mark.a.allyn@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/1] crypto: api.c adding kernel-doc comments
Date: Thu, 4 Nov 2010 10:22:19 -0700 [thread overview]
Message-ID: <20101104102219.7ec24969.rdunlap@xenotime.net> (raw)
In-Reply-To: <1288890442-11208-1-git-send-email-mark.a.allyn@intel.com>
On Thu, 4 Nov 2010 10:07:22 -0700 Mark Allyn wrote:
> Add comments to crypto_alg_lookup and crypto_larval_lookup
>
> I am re-submitting this due to errors
>
> Signed-off-by: Mark A. Allyn <mark.a.allyn@intel.com>
> ---
> crypto/api.c | 19 +++++++++++++++++++
> 1 files changed, 19 insertions(+), 0 deletions(-)
>
> diff --git a/crypto/api.c b/crypto/api.c
> index 033a714..71c389d 100644
> --- a/crypto/api.c
> +++ b/crypto/api.c
> @@ -193,6 +193,15 @@ static struct crypto_alg *crypto_larval_wait(struct crypto_alg *alg)
> return alg;
> }
>
> +/**
> + * crypto_alg_lookup() return crypto_alg structure for an algorithm
needs hyphen between function name and "return".
> + * @name: text string containing name of algorithm
> + * @type: crypto type (defined at about line 31 of
> + * include/linux/crypto.h)
> + * @mask: mask of allowable crypto types (use or'd list
> + * of types as defined at about line 31 of
> + * include/linux/crypto.h)
drop the line numbers...
> + */
> struct crypto_alg *crypto_alg_lookup(const char *name, u32 type, u32 mask)
> {
> struct crypto_alg *alg;
> @@ -205,6 +214,16 @@ struct crypto_alg *crypto_alg_lookup(const char *name, u32 type, u32 mask)
> }
> EXPORT_SYMBOL_GPL(crypto_alg_lookup);
>
> +/**
> + * crypto_alg_larval lookup() return large value (larval) crypto_alg
* crypto_larval_lookup() - return large value (larval) crypto_alg
> + * structure for an algorithm
> + * @name: text string containing name of algorithm
> + * @type: crypto type (defined at about line 31 of
> + * include/linux/crypto.h)
> + * @mask: mask of allowable crypto types (use or'd list
> + * of types as defined at about line 31 of
> + * include/linux/crypto.h)
> + */
drop the line numbers.
> struct crypto_alg *crypto_larval_lookup(const char *name, u32 type, u32 mask)
> {
> struct crypto_alg *alg;
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-11-04 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 17:07 Mark Allyn
2010-11-04 17:22 ` Randy Dunlap [this message]
2010-11-04 17:25 ` Allyn, Mark A
2010-11-04 17:30 ` Randy Dunlap
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=20101104102219.7ec24969.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.allyn@intel.com \
/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
all inboxes | Powered by JetHome®