public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Shachar Raindel <raindel-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
	<roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V1 for-next 1/9] IB/core: Introduce peer client interface
Date: Mon, 13 Oct 2014 12:32:09 +0200	[thread overview]
Message-ID: <543BAA29.4020006@acm.org> (raw)
In-Reply-To: <c8f2826c385e413eaa5f442cdcb64eaa-Vl31pUvGNwELId+1UC+8EGu6+pknBqLbXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>

On 10/12/14 14:03, Shachar Raindel wrote:
>> The kernel-doc output for the above comment block is incomplete. Please
>> fix this, and please also fix the warnings reported by the kernel-doc
>
> We are not sure what is the best way to document an operations struct
> using nanodocs.
> Looking at mmu_notifiers, they are documented inline, using a
> comment style that nanodoc can't parse
> (http://lxr.free-electrons.com/source/include/linux/mmu_notifier.h#L27 )
> Looking at the file_operations struct, there is no documentation
> whatsoever
> (http://lxr.free-electrons.com/source/include/linux/fs.h#L1482 )
> Looking at ib_device
> (http://lxr.free-electrons.com/source/include/rdma/ib_verbs.h#L1436 ),
> again there is no documentation.
>
> I attach our current nanodoc parsable comment. No errors are now
> generated when running kernel-doc on the attached file.
> Is this what you are aiming at? Can you give an example for the proper
> way to format such comments?

Hello Sachar,

Please note that I'm not an expert with regard to kernel documentation 
formats. In my opinion the documentation in the attached header file is 
not only easy to read for humans but the scripts/kernel-doc tool also 
generates nicely formatted HTML documentation from that document so I'm 
happy with the documentation format that is used in that header file.

Bart.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-10-13 10:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 13:26 [PATCH V1 for-next 0/9] Peer-Direct support Yishai Hadas
     [not found] ` <1412602019-30659-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-10-06 13:26   ` [PATCH V1 for-next 1/9] IB/core: Introduce peer client interface Yishai Hadas
     [not found]     ` <54350284.10107@acm.org>
     [not found]       ` <54350284.10107-HInyCGIudOg@public.gmane.org>
2014-10-12 12:03         ` Shachar Raindel
     [not found]           ` <c8f2826c385e413eaa5f442cdcb64eaa-Vl31pUvGNwELId+1UC+8EGu6+pknBqLbXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2014-10-13 10:32             ` Bart Van Assche [this message]
2014-10-06 13:26   ` [PATCH V1 for-next 2/9] IB/core: Get/put peer memory client Yishai Hadas
2014-10-06 13:26   ` [PATCH V1 for-next 3/9] IB/core: Umem tunneling peer memory APIs Yishai Hadas
2014-10-06 13:26   ` [PATCH V1 for-next 4/9] IB/core: Infrastructure to manage peer core context Yishai Hadas
2014-10-06 13:26   ` [PATCH V1 for-next 5/9] IB/core: Invalidation support for peer memory Yishai Hadas
2014-10-06 13:26   ` [PATCH V1 for-next 6/9] IB/core: Sysfs " Yishai Hadas
     [not found]     ` <1412602019-30659-7-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-10-06 21:00       ` Jason Gunthorpe
     [not found]         ` <20141006210023.GC28962-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2014-10-07 12:33           ` Shachar Raindel
2014-10-06 13:26   ` [PATCH V1 for-next 7/9] IB/mlx4: Invalidation support for MR over " Yishai Hadas
2014-10-06 13:26   ` [PATCH V1 for-next 8/9] IB/mlx5: " Yishai Hadas
2014-10-06 13:26   ` [PATCH V1 for-next 9/9] Samples: Peer memory client example Yishai Hadas
2014-10-06 15:12   ` [PATCH V1 for-next 0/9] Peer-Direct support Steve Wise
     [not found]     ` <5432B149.7060202-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2014-10-06 20:24       ` Or Gerlitz
     [not found]         ` <CAJ3xEMg=AeeQemGU7hL05=o9vOHHY2Xum=B7ewhUGFZr7OCyuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-06 20:38           ` Steve Wise

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=543BAA29.4020006@acm.org \
    --to=bvanassche-hinycgiudog@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=raindel-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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