All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-media@vger.kernel.org
Subject: How to fix DocBook parsers for private fields inside #ifdefs
Date: Thu, 1 Oct 2015 14:21:07 -0300	[thread overview]
Message-ID: <20151001142107.5a0bf7b2@recife.lan> (raw)

Hi Jon,


I'm trying to cleanup some warnings when creating docbooks for a struct located
at include/media/videobuf2-core.h. 

This is the struct:

struct vb2_buffer {
        struct vb2_queue        *vb2_queue;
        unsigned int            index;
        unsigned int            type;
        unsigned int            memory;
        unsigned int            num_planes;
        struct vb2_plane        planes[VIDEO_MAX_PLANES];

        /* Private: internal use only */
        enum vb2_buffer_state   state;

        struct list_head        queued_entry;
        struct list_head        done_entry;
#ifdef CONFIG_VIDEO_ADV_DEBUG
        /*
         * Counters for how often these buffer-related ops are
         * called. Used to check for unbalanced ops.
         */
        u32             cnt_mem_alloc;
...
#endif
}

The data at the ifdef are used only for debugging purposes during driver
development or driver testing and should not be used in production.

They're all after a private comment:
	/* Private: internal use only */

So, according with Documentation/kernel-doc-nano-HOWTO.txt, they shold
have been ignored.

Still, the scripts produce warnings for them:

$ make cleandocs
$ make DOCBOOKS=device-drivers.xml htmldocs 2>&1|grep /media/

.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_alloc'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_put'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_get_dmabuf'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_get_userptr'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_put_userptr'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_prepare'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_finish'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_attach_dmabuf'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_detach_dmabuf'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_map_dmabuf'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_unmap_dmabuf'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_vaddr'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_cookie'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_num_users'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_mem_mmap'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_buf_init'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_buf_prepare'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_buf_finish'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_buf_cleanup'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_buf_queue'
.//include/media/videobuf2-core.h:254: warning: No description found for parameter 'cnt_buf_done'

I tried to add another private: after the #ifdef, but it still produces
those warnings.

Any idea about how to fix it?

Thanks!
Mauro

             reply	other threads:[~2015-10-01 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 17:21 Mauro Carvalho Chehab [this message]
2015-10-05 10:56 ` How to fix DocBook parsers for private fields inside #ifdefs Jonathan Corbet
2015-10-05 12:03   ` Mauro Carvalho Chehab
2015-10-05 12:35     ` kbuild test robot
2015-10-11 21:38     ` Jonathan Corbet

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=20151001142107.5a0bf7b2@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-media@vger.kernel.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.