From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-doc@vger.kernel.org, Jani Nikula <jani.nikula@intel.com>
Subject: Re: Troubles with kernel-doc and RST files
Date: Tue, 19 Jul 2016 21:08:08 -0300 [thread overview]
Message-ID: <20160719210808.4fd591cb@recife.lan> (raw)
In-Reply-To: <20160719170133.416c94d8@lwn.net>
Em Tue, 19 Jul 2016 17:01:33 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Sun, 17 Jul 2016 10:01:54 -0300
> Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
>
> > 2) For functions, kernel-doc is now an all or nothing. If not all
> > functions are declared, it outputs this warning:
> >
> > ./include/media/media-devnode.h:1: warning: no structured comments
> >
> > And give up. No functions are exported, nor it points where it bailed.
> > So, we need to manually look into all exported symbols to identify
> > what's missing
>
> So could you describe this one in a bit more detail? An example of a
> file with the problem and associated kernel-doc directive would be most
> helpful here. This sounds like something we definitely want to fix.
I actually noticed it when I was checking for the documentation generated
by the RC header file. There, I had to add documentation for several
functions:
https://git.linuxtv.org/media_tree.git/commit/?h=docs-next&id=5b6137dc84f627e8497e554890ae02378c54f9f0
Without that, I had an error like the above, and no functions were
documented.
I didn't further tried to investigate the root cause.
One thing I noticed is that Sphinx is very poor on detecting some types
of changes, and we need to wipe out the Sphinx docs after some changes,
as otherwise the document won't be ok. Maybe that's the case.
Another possibility is that the all or nothing behavior happens when
the :export: attribute is used.
Thanks,
Mauro
next prev parent reply other threads:[~2016-07-20 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 13:01 Troubles with kernel-doc and RST files Mauro Carvalho Chehab
2016-07-18 2:37 ` Jonathan Corbet
2016-07-18 11:54 ` Mauro Carvalho Chehab
2016-07-19 10:00 ` Markus Heiser
2016-07-19 22:58 ` Jonathan Corbet
2016-07-20 5:32 ` Markus Heiser
2016-07-19 23:01 ` Jonathan Corbet
2016-07-20 0:08 ` Mauro Carvalho Chehab [this message]
2016-07-19 23:16 ` Jonathan Corbet
2016-07-20 0:09 ` Mauro Carvalho Chehab
2016-07-20 5:35 ` Markus Heiser
2016-07-19 23:30 ` Jonathan Corbet
2016-07-20 0:19 ` Mauro Carvalho Chehab
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=20160719210808.4fd591cb@recife.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).