From: "Christian König" <deathsimple@vodafone.de>
To: alexdeucher@gmail.com
Cc: Alex Deucher <alexander.deucher@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 00/10] Start documenting the radeon drm better
Date: Fri, 29 Jun 2012 16:39:24 +0200 [thread overview]
Message-ID: <4FEDBE1C.3050904@vodafone.de> (raw)
In-Reply-To: <1340980110-10784-1-git-send-email-alexdeucher@gmail.com>
On 29.06.2012 16:28, alexdeucher@gmail.com wrote:
> 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?
Sounds like a good idea to me, but could we move the old and deprecated
non KMS code into it's own subdirectory or something like that first?
Also for some files it might be a good idea to spread them into separate
ones first, like the gart and vm and/or the ring and ib stuff.
Cheers,
Christian.
>
> Alex Deucher (10):
> drm/radeon: document radeon_device.c
> drm/radeon: document radeon_kms.c
> drm/radeon: document radeon_irq_kms.c
> drm/radeon: document radeon_asic.c
> drm/radeon: document radeon_fence.c
> drm/radeon: document radeon_ring.c
> drm/radeon: document non-VM functions in radeon_gart.c
> drm/radeon: document VM functions in radeon_gart.c
> drm/radeon: start to document the functions r100.c
> drm/radeon: start to document evergreen.c
>
> drivers/gpu/drm/radeon/evergreen.c | 120 ++++++++++
> drivers/gpu/drm/radeon/r100.c | 127 ++++++++++-
> drivers/gpu/drm/radeon/radeon_asic.c | 46 ++++
> drivers/gpu/drm/radeon/radeon_device.c | 344 +++++++++++++++++++++++++++-
> drivers/gpu/drm/radeon/radeon_fence.c | 373 +++++++++++++++++++++++++++++
> drivers/gpu/drm/radeon/radeon_gart.c | 391 ++++++++++++++++++++++++++++++-
> drivers/gpu/drm/radeon/radeon_irq_kms.c | 150 ++++++++++++
> drivers/gpu/drm/radeon/radeon_kms.c | 126 ++++++++++
> drivers/gpu/drm/radeon/radeon_ring.c | 374 +++++++++++++++++++++++++++++-
> 9 files changed, 2041 insertions(+), 10 deletions(-)
>
next prev parent reply other threads:[~2012-06-29 14:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 14:28 [PATCH 00/10] Start documenting the radeon drm better alexdeucher
2012-06-29 14:28 ` [PATCH 01/10] drm/radeon: document radeon_device.c alexdeucher
2012-06-29 14:28 ` [PATCH 02/10] drm/radeon: document radeon_kms.c alexdeucher
2012-06-29 14:28 ` [PATCH 03/10] drm/radeon: document radeon_irq_kms.c alexdeucher
2012-06-29 14:28 ` [PATCH 04/10] drm/radeon: document radeon_asic.c alexdeucher
2012-06-29 14:28 ` [PATCH 05/10] drm/radeon: document radeon_fence.c alexdeucher
2012-06-29 15:05 ` Christian König
2012-06-29 14:28 ` [PATCH 06/10] drm/radeon: document radeon_ring.c alexdeucher
2012-06-29 14:28 ` [PATCH 07/10] drm/radeon: document non-VM functions in radeon_gart.c alexdeucher
2012-06-29 14:28 ` [PATCH 08/10] drm/radeon: document VM " alexdeucher
2012-06-29 14:28 ` [PATCH 09/10] drm/radeon: start to document the functions r100.c alexdeucher
2012-06-29 14:28 ` [PATCH 10/10] drm/radeon: start to document evergreen.c alexdeucher
2012-06-29 14:39 ` Christian König [this message]
2012-06-29 14:53 ` [PATCH 00/10] Start documenting the radeon drm better Alex Deucher
2012-06-29 14:42 ` Tom Stellard
2012-06-29 14:51 ` Alex Deucher
2012-06-29 15:45 ` Rafał Miłecki
2012-06-29 16:50 ` [PATCH 01/10] drm/radeon: document radeon_device.c (v2) alexdeucher
2012-06-29 16:50 ` [PATCH 02/10] drm/radeon: document radeon_kms.c alexdeucher
2012-06-29 16:50 ` [PATCH 03/10] drm/radeon: document radeon_irq_kms.c alexdeucher
2012-06-29 16:50 ` [PATCH 04/10] drm/radeon: document radeon_asic.c alexdeucher
2012-06-29 16:50 ` [PATCH 05/10] drm/radeon: document radeon_fence.c (v2) alexdeucher
2012-06-29 16:50 ` [PATCH 06/10] drm/radeon: document radeon_ring.c (v2) alexdeucher
2012-06-29 16:50 ` [PATCH 07/10] drm/radeon: document non-VM functions in radeon_gart.c (v2) alexdeucher
2012-06-29 16:50 ` [PATCH 08/10] drm/radeon: document VM " alexdeucher
2012-06-29 16:50 ` [PATCH 09/10] drm/radeon: start to document the functions r100.c alexdeucher
2012-06-29 16:50 ` [PATCH 10/10] drm/radeon: start to document evergreen.c alexdeucher
2012-07-02 10:45 ` [PATCH 01/10] drm/radeon: document radeon_device.c (v2) Christian König
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=4FEDBE1C.3050904@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--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.