From: Doug Ledford <dledford@redhat.com>
To: Michael Wang <yun.wang@profitbricks.com>
Cc: Or Gerlitz <gerlitz.or@gmail.com>,
Roland Dreier <roland@kernel.org>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal@dev.mellanox.co.il>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>,
Ira Weiny <ira.weiny@intel.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Subject: Re: [PATCH RFC v2] Documentation/infiniband: Add docs for rdma-helpers
Date: Mon, 18 May 2015 12:58:11 -0400 [thread overview]
Message-ID: <1431968291.3114.13.camel@redhat.com> (raw)
In-Reply-To: <555A04C8.10802@profitbricks.com>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
On Mon, 2015-05-18 at 17:27 +0200, Michael Wang wrote:
>
> On 05/18/2015 05:21 PM, Doug Ledford wrote:
> [snip]
> >>
> >> I'll put the highlights and changelog under '---' in next version, is it
> >> looks like this?
> >
> > We're still missing Jason's feedback request though. Specifically, he
> > pointed out that kdocs are usually not done in Documentation/*, they are
> > done in the .c files where the function is (or the .h file if the
> > function is an inline, which these all are). So, you included some
> > limited documentation for each of these items in your original patches
> > that added them. His request was that you put this expanded information
> > not in Documentation/infiniband where someone has to go looking for it,
> > but as part of the kdoc header for each of the various helpers in
> > ib_verbs.h itself.
>
> I see :-) I've not work with the kdoc yet, not sure if there is any
> guidelines on how to write the header of inline func for kdoc?
It's an automated tool thing. Any comment section that starts with /**
is automatically included as a kdoc. Then there is an expected format
after that. See Documentation/kernel-doc-nano-HOWTO.txt.
> >
> > Just because I want to move this along versus waiting for another
> > respin, I'm going to copy and paste these into those locations and clean
> > up the changelog when I integrate this patch.
>
> Got it, if there is anything I could help, please let me know ;-)
I'm sending the patch for review, please let me know if you are OK with
how I handled the attribution.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: 0E572FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-18 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 8:41 [PATCH RFC v2] Documentation/infiniband: Add docs for rdma-helpers Michael Wang
2015-05-18 9:47 ` Or Gerlitz
2015-05-18 10:06 ` Michael Wang
2015-05-18 15:21 ` Doug Ledford
[not found] ` <1431962485.3114.8.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-18 15:27 ` Michael Wang
2015-05-18 15:27 ` Michael Wang
2015-05-18 16:58 ` Doug Ledford [this message]
[not found] ` <1431968291.3114.13.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-18 17:02 ` [PATCH] IB/Verbs: Improve " Doug Ledford
2015-05-19 7:56 ` [PATCH RFC v2] Documentation/infiniband: Add " Michael Wang
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=1431968291.3114.13.camel@redhat.com \
--to=dledford@redhat.com \
--cc=gerlitz.or@gmail.com \
--cc=hal@dev.mellanox.co.il \
--cc=ira.weiny@intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=yun.wang@profitbricks.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.