From: Michael Wang <yun.wang@profitbricks.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Roland Dreier <roland@kernel.org>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal@dev.mellanox.co.il>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>,
Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH RFC] Documentation/infiniband: Add docs for rdma-helpers
Date: Fri, 15 May 2015 09:51:50 +0200 [thread overview]
Message-ID: <5555A596.5050709@profitbricks.com> (raw)
In-Reply-To: <20150513155915.GB16941@obsidianresearch.com>
On 05/13/2015 05:59 PM, Jason Gunthorpe wrote:
> On Wed, May 13, 2015 at 03:24:32PM +0200, Michael Wang wrote:
>> This is the following patch for:
>> https://lkml.org/lkml/2015/5/5/417
>> which try to document the settled rdma_cap_XX().
>>
>> Highlights:
>> There could be many missing/mistakes/misunderstanding, please don't
>> be hesitate to point out the issues, any suggestions to improve or
>> complete the description are very welcomed ;-)
>
> I'd rather see this in the kdoc for each function.
I used to thought you mean the kernel documentation like
this... my misunderstanding but this is the usual way to
document kernel stuff, isn't it?
BTW, could you give more details on the kdoc?
Regards,
Michael Wang
>
> Thanks,
> Jason
>
prev parent reply other threads:[~2015-05-15 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 13:24 [PATCH RFC] Documentation/infiniband: Add docs for rdma-helpers Michael Wang
[not found] ` <1431523472-10888-1-git-send-email-yun.wang-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2015-05-13 15:11 ` Doug Ledford
2015-05-13 16:42 ` Hefty, Sean
2015-05-15 8:31 ` Michael Wang
[not found] ` <5555AEE5.9060503-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2015-05-15 14:40 ` Doug Ledford
[not found] ` <1431700819.27722.15.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-15 15:02 ` Michael Wang
[not found] ` <1431529914.2377.22.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-15 8:12 ` Michael Wang
[not found] ` <5555AA7D.7080503-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2015-05-15 14:27 ` Doug Ledford
[not found] ` <1431700060.27722.7.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-15 14:38 ` Michael Wang
2015-05-13 15:59 ` Jason Gunthorpe
2015-05-15 7:51 ` 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=5555A596.5050709@profitbricks.com \
--to=yun.wang@profitbricks.com \
--cc=dledford@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox