All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Robert Love <robert.w.love@intel.com>
Cc: james.bottomley@hansenpartnership.com,
	linux-scsi@vger.kernel.org, jgarzik@redhat.com,
	davem@davemloft.net, james.smart@emulex.com,
	michaelc@cs.wisc.edu, jeykholt@cisco.com, andi@firstfloor.org,
	jeffrey.t.kirsher@intel.com,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH 3/3] fcoe: Fibre Channel over Ethernet
Date: Fri, 6 Feb 2009 11:13:01 -0800	[thread overview]
Message-ID: <20090206111301.67ddac2d.akpm@linux-foundation.org> (raw)
In-Reply-To: <1233947117.7785.5.camel@fritz>

On Fri, 06 Feb 2009 11:05:17 -0800
Robert Love <robert.w.love@intel.com> wrote:

> > The kerneldoc comments consistently close with
> > 
> > **/
> > 
> > which is consistently unconventional.  Not wrong, just odd.
> > 
> 
> I did change the kernel-doc function comment blocks to end with '*/',
> since you called it out. I looked at the other comments under
> drivers/scsi/ and most did end in '*/'. However, the
> Documentation/kernel-doc-nano-HOWTO.txt has an example for function
> headers that shows '**/' as the suggested style. Should the kernel-doc
> HOWTO be updated?

I think so - we might as well be consistent about these things.

> Example kernel-doc function comment:
> 
> /**
>  * foobar() - short function description of foobar
>  * @arg1:       Describe the first argument to foobar.
>  * @arg2:       Describe the second argument to foobar.
>  *              One can provide multiple line descriptions
>  *              for arguments.
>  *
>  * A longer description, with more discussion of the function foobar()
>  * that might be useful to those using or modifying it.  Begins with
>  * empty comment line, and may include additional embedded empty
>  * comment lines.
>  *
>  * The longer description can have multiple paragraphs.
>  **/

That's RandyStuff.

  reply	other threads:[~2009-02-06 19:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 23:10 [PATCH 0/3] Open-FCoE Submission (round 2) Robert Love
2008-12-09 23:10 ` [PATCH 1/3] FC protocol definition header files Robert Love
2008-12-09 23:10 ` [PATCH 2/3] libfc: A modular Fibre Channel library Robert Love
2008-12-10  0:03   ` Andi Kleen
2008-12-10 18:42     ` Vasu Dev
2008-12-10 19:42       ` Andi Kleen
2008-12-12  1:55         ` Vasu Dev
2008-12-12  2:19           ` Joe Eykholt
2008-12-11  0:44     ` Chris Leech
2008-12-11  0:49     ` Chris Leech
2008-12-11 20:32     ` Zou, Yi
2008-12-11 23:33       ` Andi Kleen
2008-12-09 23:10 ` [PATCH 3/3] fcoe: Fibre Channel over Ethernet Robert Love
2009-02-05  2:24   ` Andrew Morton
2009-02-06 19:05     ` Robert Love
2009-02-06 19:13       ` Andrew Morton [this message]
2009-02-06 19:26         ` [PATCH] kernel-doc: preferred ending marker and examples Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2008-11-18 22:20 [PATCH 0/3] Open-FCoE Submission Robert Love
2008-11-18 22:21 ` [PATCH 3/3] fcoe: Fibre Channel over Ethernet Robert Love

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=20090206111301.67ddac2d.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=davem@davemloft.net \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=james.smart@emulex.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jeykholt@cisco.com \
    --cc=jgarzik@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=randy.dunlap@oracle.com \
    --cc=robert.w.love@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 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.