From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Smart <James.Smart@emulex.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 3/14] lpfc 8.3.0 : Add kernel-doc headers to lpfc_scsi.c
Date: Fri, 05 Dec 2008 09:25:20 -0800 [thread overview]
Message-ID: <49396400.7020508@oracle.com> (raw)
In-Reply-To: <493962D5.9010103@emulex.com>
James Smart wrote:
> Randy,
>
> Thanks. Looks like we have this mistake in quite a few places.
>
> Any issue if we proceed with this patch set as is, and I'll turn around
> and issue another set that addresses the kernel-doc style explicitly ?
That's OK with me if it's done soon.
> -- james s
>
>
> Randy Dunlap wrote:
>> James Smart wrote:
>>> lpfc 8.3.0 : Add kernel-doc function headers to lpfc_scsi.c
>>>
>>> Add kernel-doc function headers to lpfc_scsi.c
>>>
>>
>> Hi James,
>>
>> kernel-doc is a small language, with a small bit of syntax. It's
>> documented
>> in Documentation/kernel-doc-nano-HOWTO.txt.
>>
>> I say this because all of the first lines (function name/short
>> description)
>> use : instead of - to separate the name from the description.
>> Please fix those.
>>
>> Also, the function name/short description can only be one line, so
>> either make
>> it > 80 characters if needed, or use this format:
>>
>> /**
>> * lpfc_snaz - do some snazzy stuff
>> * @hba: the target hba
>> *
>> * lpfc_snaz does some cool stuff and some hot stuff, such as-
>> * - system snapshot to hba memory
>> * - system check for infections and intrusions
>> * - starts the coffee maker
>> **/
prev parent reply other threads:[~2008-12-05 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 3:39 [PATCH 3/14] lpfc 8.3.0 : Add kernel-doc headers to lpfc_scsi.c James Smart
2008-12-05 16:31 ` Randy Dunlap
2008-12-05 17:20 ` James Smart
2008-12-05 17:25 ` Randy Dunlap [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=49396400.7020508@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=James.Smart@emulex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.