All of lore.kernel.org
 help / color / mirror / Atom feed
From: Archit Taneja <architt@codeaurora.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org,
	airlied@redhat.com, andy.yan@rock-chips.com,
	ajaykumar.rs@samsung.com
Subject: Re: [PATCH v3 2/2] drm: bridge: Add missing headerdocs for older bridge functions
Date: Tue, 19 May 2015 16:40:08 +0530	[thread overview]
Message-ID: <555B1A10.7010304@codeaurora.org> (raw)
In-Reply-To: <20150519093719.GM15256@phenom.ffwll.local>



On 05/19/2015 03:07 PM, Daniel Vetter wrote:
> On Tue, May 19, 2015 at 02:05:05PM +0530, Archit Taneja wrote:
>> Add headerdocs for drm_bridge_add, drm_bridge_remove, drm_bridge_attach and
>> of_drm_find_bridge.
>>
>> Signed-off-by: Archit Taneja <architt@codeaurora.org>
>
> You also need to pull in the kerneldoc into the drm.tmpl DocBook template
> to include into the drm docs. You can generate those with
>
> $ make htmldocs -k
>
> -k because right now 802 docs are broken :( Also it'd be awesome if you
> could include a short DOC: section to describe the design&goal of
> drm_bridge quickly and also include that into the DocBook.
>
>> ---
>>   drivers/gpu/drm/drm_bridge.c | 28 ++++++++++++++++++++++++++++
>>   1 file changed, 28 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm/drm_bridge.c
>> index f70e617..ceb8121 100644
>> --- a/drivers/gpu/drm/drm_bridge.c
>> +++ b/drivers/gpu/drm/drm_bridge.c
>> @@ -31,6 +31,11 @@
>>   static DEFINE_MUTEX(bridge_lock);
>>   static LIST_HEAD(bridge_list);
>>
>> +/**
>> + * drm_bridge_add - add the given bridge to the global bridge list
>> + *
>> + * @bridge: bridge control structure
>
> For functions which return something it's good to add a Returns: section
> describing the semantics of the return codes. Copypasting something
> suitable from other kerneldoc is good for consistency ;-)

I wasn't aware of the template stuff. I'll do the required.

Thanks!
Archit

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-05-19 11:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  8:35 [PATCH v3 1/2] drm: bridge: Allow daisy chaining of bridges Archit Taneja
2015-05-19  8:35 ` [PATCH v3 2/2] drm: bridge: Add missing headerdocs for older bridge functions Archit Taneja
2015-05-19  9:37   ` Daniel Vetter
2015-05-19 11:10     ` Archit Taneja [this message]
2015-05-19  9:34 ` [PATCH v3 1/2] drm: bridge: Allow daisy chaining of bridges Daniel Vetter
2015-05-19 11:07   ` Archit Taneja
2015-05-19 15:30     ` Daniel Vetter
2015-05-20  5:19       ` Archit Taneja
2015-05-20  6:35         ` Daniel Vetter
2015-05-20  7:13           ` Archit Taneja
2015-05-20  7:46             ` Daniel Vetter

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=555B1A10.7010304@codeaurora.org \
    --to=architt@codeaurora.org \
    --cc=airlied@redhat.com \
    --cc=ajaykumar.rs@samsung.com \
    --cc=andy.yan@rock-chips.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.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 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.