From: Michael Wang <yun.wang@profitbricks.com>
To: Doug Ledford <dledford@redhat.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: Tue, 19 May 2015 09:56:50 +0200 [thread overview]
Message-ID: <555AECC2.70502@profitbricks.com> (raw)
In-Reply-To: <1431968291.3114.13.camel@redhat.com>
On 05/18/2015 06:58 PM, Doug Ledford wrote:
[snip]
>> 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.
Got it :-)
>
>>>
>>> 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.
The definition is far more detailed and accurate, it's already good enough
according to my understanding, should benefit the developer a lot ;-)
Regards,
Michael Wang
>
prev parent reply other threads:[~2015-05-19 7:56 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
[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 ` Michael Wang [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=555AECC2.70502@profitbricks.com \
--to=yun.wang@profitbricks.com \
--cc=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 \
/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.