dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	David Airlie <airlied@linux.ie>,
	Jani Nikula <jani.nikula@intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Sean Paul <sean@poorly.run>,
	Emil Velikov <emil.velikov@collabora.com>
Subject: Re: [PATCH] drm/doc: Document kapi doc expectations
Date: Fri, 19 Jul 2019 15:04:14 +0200	[thread overview]
Message-ID: <20190719130414.GO15868@phenom.ffwll.local> (raw)
In-Reply-To: <20190705151447.GP15868@phenom.ffwll.local>

On Fri, Jul 05, 2019 at 05:14:47PM +0200, Daniel Vetter wrote:
> On Thu, Jul 04, 2019 at 04:50:54PM +0200, Daniel Vetter wrote:
> > We've had this already for anything new. With my drm_prime.c cleanup I
> > also think documentation for everything already existing is complete,
> > and we can bake this in as a requirements subsystem wide.
> > 
> > v2: Improve wording a bit (Laurent), fix typo in commit message (Sam).
> > 
> > Acked-by: Emil Velikov <emil.velikov@collabora.com>
> > Acked-by: Sean Paul <sean@poorly.run>
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
> > Acked-by: Sam Ravnborg <sam@ravnborg.org>
> > Acked-by: Jani Nikula <jani.nikula@intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> 
> From irc:
> 
> Acked-by: Alex Deucher <alexdeucher@gmail.com>

I guess that's enough acks, applied for 5.4 in drm-misc-next.
-Daniel

> 
> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > Cc: David Airlie <airlied@linux.ie>
> > Cc: Daniel Vetter <daniel@ffwll.ch>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> > Cc: Sean Paul <sean@poorly.run>
> > ---
> >  Documentation/gpu/introduction.rst | 16 ++++++++++++++++
> >  Documentation/gpu/todo.rst         | 13 -------------
> >  2 files changed, 16 insertions(+), 13 deletions(-)
> > 
> > diff --git a/Documentation/gpu/introduction.rst b/Documentation/gpu/introduction.rst
> > index fccbe375244d..25a56e9c0cfd 100644
> > --- a/Documentation/gpu/introduction.rst
> > +++ b/Documentation/gpu/introduction.rst
> > @@ -51,6 +51,22 @@ and "FIXME" where the interface could be cleaned up.
> >  
> >  Also read the :ref:`guidelines for the kernel documentation at large <doc_guide>`.
> >  
> > +Documentation Requirements for kAPI
> > +-----------------------------------
> > +
> > +All kernel APIs exported to other modules must be documented, including their
> > +datastructures and at least a short introductory section explaining the overall
> > +concepts. Documentation should be put into the code itself as kerneldoc comments
> > +as much as reasonable.
> > +
> > +Do not blindly document everything, but document only what's relevant for driver
> > +authors: Internal functions of drm.ko and definitely static functions should not
> > +have formal kerneldoc comments. Use normal C comments if you feel like a comment
> > +is warranted. You may use kerneldoc syntax in the comment, but it shall not
> > +start with a /** kerneldoc marker. Similar for data structures, annotate
> > +anything entirely private with ``/* private: */`` comments as per the
> > +documentation guide.
> > +
> >  Getting Started
> >  ===============
> >  
> > diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> > index e717f280f9ae..db88969a56ee 100644
> > --- a/Documentation/gpu/todo.rst
> > +++ b/Documentation/gpu/todo.rst
> > @@ -301,19 +301,6 @@ In the end no .c file should need to include ``drmP.h`` anymore.
> >  
> >  Contact: Daniel Vetter
> >  
> > -Add missing kerneldoc for exported functions
> > ---------------------------------------------
> > -
> > -The DRM reference documentation is still lacking kerneldoc in a few areas. The
> > -task would be to clean up interfaces like moving functions around between
> > -files to better group them and improving the interfaces like dropping return
> > -values for functions that never fail. Then write kerneldoc for all exported
> > -functions and an overview section and integrate it all into the drm book.
> > -
> > -See https://dri.freedesktop.org/docs/drm/ for what's there already.
> > -
> > -Contact: Daniel Vetter
> > -
> >  Make panic handling work
> >  ------------------------
> >  
> > -- 
> > 2.20.1
> > 
> 
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2019-07-19 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 20:36 [PATCH] drm/doc: Document kapi doc expectations Daniel Vetter
2019-06-25 20:42 ` Sean Paul
2019-06-25 20:47 ` Sam Ravnborg
2019-07-04  8:39 ` Daniel Vetter
2019-07-04 14:01   ` Emil Velikov
2019-07-04 12:38 ` Laurent Pinchart
2019-07-04 14:50 ` Daniel Vetter
2019-07-05 15:14   ` Daniel Vetter
2019-07-19 13:04     ` Daniel Vetter [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=20190719130414.GO15868@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.velikov@collabora.com \
    --cc=jani.nikula@intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=sam@ravnborg.org \
    --cc=sean@poorly.run \
    /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