From: Jani Nikula <jani.nikula@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 1/2] Documentation/sphinx: kerneldoc: add "unused-functions"
Date: Fri, 31 Mar 2017 15:54:04 +0300 [thread overview]
Message-ID: <878tnl38ur.fsf@intel.com> (raw)
In-Reply-To: <20170331071632.6209-1-johannes@sipsolutions.net>
On Fri, 31 Mar 2017, Johannes Berg <johannes@sipsolutions.net> wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> When adding functions one by one into documentation, in order to
> order/group things properly, it's easy to miss things. Allow use
> of the kernel-doc directive with "unused-functions" like this
>
> .. kernel-doc:: <filename>
> :unused-functions:
I'm sure the parameter name could be improved to capture what you mean
better; alas I don't have a suggestion.
>
> to output anything previously unused from that file. This allows
> grouping things but still making sure that the documentation has
> all the functions.
>
> Internally this works by collecting (per-file) those functions
> (and enums, structs, doc sections...) that are explicitly used,
> and invoking the kernel-doc script with "-nofunction" later.
A quick thought that I don't have the time to check now, but should be
checked before merging: Is the order of directive extension execution
deterministic if the Sphinx run is parallelized (sphinx-build -j)? Is it
deterministic within an rst file? Surely it's not deterministic when
called from several rst files? The latter is, perhaps, acceptable, but
the former not.
BR,
Jani.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> Documentation/sphinx/kerneldoc.py | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/sphinx/kerneldoc.py b/Documentation/sphinx/kerneldoc.py
> index d15e07f36881..79fc1491348a 100644
> --- a/Documentation/sphinx/kerneldoc.py
> +++ b/Documentation/sphinx/kerneldoc.py
> @@ -41,6 +41,9 @@ from sphinx.ext.autodoc import AutodocReporter
>
> __version__ = '1.0'
>
> +# per-file list
> +_used_fns = {}
> +
> class KernelDocDirective(Directive):
> """Extract kernel-doc comments from the specified file"""
> required_argument = 1
> @@ -50,6 +53,7 @@ class KernelDocDirective(Directive):
> 'functions': directives.unchanged_required,
> 'export': directives.unchanged,
> 'internal': directives.unchanged,
> + 'unused-functions': directives.unchanged,
> }
> has_content = False
>
> @@ -60,6 +64,10 @@ class KernelDocDirective(Directive):
> filename = env.config.kerneldoc_srctree + '/' + self.arguments[0]
> export_file_patterns = []
>
> + if not filename in _used_fns:
> + _used_fns[filename] = []
> + _used_fns_this_file = _used_fns[filename]
> +
> # Tell sphinx of the dependency
> env.note_dependency(os.path.abspath(filename))
>
> @@ -73,10 +81,16 @@ class KernelDocDirective(Directive):
> cmd += ['-internal']
> export_file_patterns = str(self.options.get('internal')).split()
> elif 'doc' in self.options:
> - cmd += ['-function', str(self.options.get('doc'))]
> + f = str(self.options.get('doc'))
> + cmd += ['-function', f]
> + _used_fns_this_file.append(f)
> + elif 'unused-functions' in self.options:
> + for f in _used_fns_this_file:
> + cmd += ['-nofunction', f]
> elif 'functions' in self.options:
> for f in str(self.options.get('functions')).split():
> cmd += ['-function', f]
> + _used_fns_this_file.append(f)
>
> for pattern in export_file_patterns:
> for f in glob.glob(env.config.kerneldoc_srctree + '/' + pattern):
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-03-31 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 7:16 [PATCH 1/2] Documentation/sphinx: kerneldoc: add "unused-functions" Johannes Berg
2017-03-31 7:16 ` [PATCH 2/2] cfg80211: add remaining functions/etc. to documentation Johannes Berg
2017-03-31 8:39 ` [PATCH 1/2] Documentation/sphinx: kerneldoc: add "unused-functions" Markus Heiser
2017-03-31 8:42 ` Johannes Berg
2017-03-31 12:54 ` Jani Nikula [this message]
2017-04-03 19:59 ` Johannes Berg
2017-04-04 7:26 ` Jani Nikula
2017-05-30 13:23 ` Johannes Berg
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=878tnl38ur.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-wireless@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 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).