[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dri-devel
Subject:    Re: [PATCH 00/10] Start documenting the radeon drm better
From:       Rafał Miłecki <zajec5 () gmail ! com>
Date:       2012-06-29 15:45:51
Message-ID: CACna6rzjdpf0nzjN9z7f9kk59_8XE7Hnxny9H-c_VaYs9tOocA () mail ! gmail ! com
[Download RAW message or body]

2012/6/29  <alexdeucher@gmail.com>:
> From: Alex Deucher <alexander.deucher@amd.com>
>
> This is something I've been wanting to do for a while and
> I finally spent a little time getting a start on it.  There
> is still a lot to do and not all of my descriptions are great,
> but I think we can document the rest in bits and pieces. I
> also added a note about what asics the function is applicable
> to. I tried to start with the more common and complex code.
> I was thinking it would make sense to have an informal
> documentation policy something like the following:
> 1. If you edit an undocumented function, add documentation
> 2. If you edit a documented function and change how it works,
>   update the documentation
> 3. All new functions added should be documented
>
> Fulfulling all of these for stable fixes could pose problems
> so obviously there is some leeway.
>
> Thoughts?

I'd try to avoid repeating definitions over and over, but generally
THIS IS GREAT. Thanks a lot for doing that!

-- 
Rafał
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[prev in list] [next in list] [prev in thread] [next in thread]