From: Johannes Berg <johannes@sipsolutions.net>
To: Jani Nikula <jani.nikula@linux.intel.com>,
linux-wireless@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation/sphinx: kerneldoc: add "unused-functions"
Date: Mon, 03 Apr 2017 21:59:33 +0200 [thread overview]
Message-ID: <1491249573.4714.3.camel@sipsolutions.net> (raw)
In-Reply-To: <878tnl38ur.fsf@intel.com>
On Fri, 2017-03-31 at 15:54 +0300, Jani Nikula wrote:
>
> I'm sure the parameter name could be improved to capture what you
> mean better; alas I don't have a suggestion.
Yes, that's a fair point - perhaps "functions-not-linked" or something
like that.
> > 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.
Interesting, TBH I never even considered this. How would I even run it
that way? Presumably "make htmldocs" doesn't do this?
Sphinx documentation (http://www.sphinx-doc.org/en/stable/extdev/) says
this:
The setup() function can return a dictionary. This is treated by
Sphinx as metadata of the extension. Metadata keys currently
recognized are:
[...]
'parallel_read_safe': a boolean that specifies if parallel reading
of source files can be used when the extension is loaded. It
defaults to False, i.e. you have to explicitly specify your
extension to be parallel-read-safe after checking that it is.
We do set this right now, so I guess it'd only be guaranteed to work
right within a single rst file, and then I should perhaps consider not
making this state global but somehow linking it to the rst file being
processed?
johannes
next prev parent reply other threads:[~2017-04-03 19:59 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
2017-04-03 19:59 ` Johannes Berg [this message]
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=1491249573.4714.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jani.nikula@linux.intel.com \
--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 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.