[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <555AECC2.70502@profitbricks.com>
Date: Tue, 19 May 2015 09:56:50 +0200
From: Michael Wang <yun.wang@...fitbricks.com>
To: Doug Ledford <dledford@...hat.com>
CC: Or Gerlitz <gerlitz.or@...il.com>,
Roland Dreier <roland@...nel.org>,
Sean Hefty <sean.hefty@...el.com>,
Hal Rosenstock <hal@....mellanox.co.il>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-doc@...r.kernel.org, Or Gerlitz <ogerlitz@...lanox.com>,
Ira Weiny <ira.weiny@...el.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>
Subject: Re: [PATCH RFC v2] Documentation/infiniband: Add docs for rdma-helpers
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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists