mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Tasos Parisinos <t.parisinos@sciensis.com>,
	herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1][NEW] crypto API: rsa algorithm module patch (kernel version 2.6.20.3)
Date: Wed, 21 Mar 2007 09:30:29 -0700	[thread overview]
Message-ID: <20070321093029.5668cd99.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703211207170.7576@localhost.localdomain>

On Wed, 21 Mar 2007 12:08:58 -0400 (EDT) Robert P. J. Day wrote:

> On Wed, 21 Mar 2007, Randy Dunlap wrote:
> 
> > On Wed, 21 Mar 2007 17:13:31 +0200 (EET) Tasos Parisinos wrote:
> 
> > > +/*
> > > + * mpi_alloc - allocate an mpi
> > > + * @n: pointer pointer to the allocated mpi
> > > + * @limbs: number of allocated limbs (32 bit digits)
> > > + *
> > > + * The allocated mpi will be zeroed and not canonicalized
> > > + */
> 
> 
> if this is extractable kernel doc content, shouldn't it begin with
> "/**" rather than just "/*"?

Yes, so it's not extractable.  However, I also asked which functions
are meant to be exported, and those are the ones that really need to
be in kernel-doc format IMO.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-03-21 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 15:13 Tasos Parisinos
2007-03-21 16:04 ` Randy Dunlap
2007-03-21 16:08   ` Robert P. J. Day
2007-03-21 16:30     ` Randy Dunlap [this message]
2007-03-22  8:36   ` Tasos Parisinos
2007-03-22 17:46     ` Randy Dunlap
2007-03-22 22:36 ` Indan Zupancic

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=20070321093029.5668cd99.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=t.parisinos@sciensis.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®