public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: scsi <linux-scsi@vger.kernel.org>
Cc: Sumant.Patro@lsi.com, jejb <james.bottomley@steeleye.com>,
	akpm <akpm@osdl.org>
Subject: Re: [PATCH] megaraid: fix kernel-doc
Date: Fri, 5 Jan 2007 22:46:49 -0800	[thread overview]
Message-ID: <20070105224649.6bc9ea26.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070105224148.c4bb945a.randy.dunlap@oracle.com>

On Fri, 5 Jan 2007 22:41:48 -0800 Randy Dunlap wrote:

> From: Randy Dunlap <randy.dunlap@oracle.com>

Oh, this applies on top of today's patch from Sumant (which Andrew
has put into -mm)...


> kernel-doc modifications:
> - change "@param var" notation to @var;
> - change function/description separator from ':' to '-';
> - change var/description separator from '-' to ':';
> - fix a few doc. typos;
> - don't use kernel-doc /** lead-in when the doc. block is not kernel-doc;
> - use Linux common */ ending comment format instead of **/;
> - use correct function parameter names;
> - place function parameters immediately after the function short description;
> - place kernel-doc immediately before its function or macro;
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  drivers/scsi/megaraid/mega_common.h    |  120 ++++++-------
>  drivers/scsi/megaraid/megaraid_ioctl.h |   36 ++--
>  drivers/scsi/megaraid/megaraid_mbox.c  |  285 ++++++++++++++++-----------------
>  drivers/scsi/megaraid/megaraid_mbox.h  |   42 ++--
>  drivers/scsi/megaraid/megaraid_mm.c    |   65 +++----
>  drivers/scsi/megaraid/megaraid_sas.h   |   14 -
>  6 files changed, 275 insertions(+), 287 deletions(-)


---
~Randy

  reply	other threads:[~2007-01-06  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06  6:41 [PATCH] megaraid: fix kernel-doc Randy Dunlap
2007-01-06  6:46 ` Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-12 23:28 Patro, Sumant

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=20070105224649.6bc9ea26.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=Sumant.Patro@lsi.com \
    --cc=akpm@osdl.org \
    --cc=james.bottomley@steeleye.com \
    --cc=linux-scsi@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