From: Jonathan Corbet <corbet@lwn.net>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Amol Grover <frextrite@gmail.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
rcu@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Shuah Khan <skhan@linuxfoundation.org>,
Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>
Subject: Re: [PATCH] doc: listRCU: Add some more listRCU patterns in the kernel
Date: Wed, 4 Dec 2019 08:47:29 -0700 [thread overview]
Message-ID: <20191204084729.184480f3@lwn.net> (raw)
In-Reply-To: <20191204153958.GA17404@google.com>
On Wed, 4 Dec 2019 10:39:58 -0500
Joel Fernandes <joel@joelfernandes.org> wrote:
> Actually I had asked Amol privately to add the backticks. It appeared
> super weird in my browser when some function calls were rendered
> monospace while others weren't. Not all functions were successfully
> cross referenced for me. May be it is my kernel version?
If you have an example of a failure to cross-reference a function that
has kerneldoc comments *that are included in the toctree*, I'd like to see
it; that's a bug.
Changing the font on functions without anything to cross-reference to is
easy enough and should probably be done; I'll look into it when I get a
chance.
Thanks,
jon
next prev parent reply other threads:[~2019-12-04 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 6:39 [PATCH] doc: listRCU: Add some more listRCU patterns in the kernel Amol Grover
2019-12-03 13:41 ` Jonathan Corbet
2019-12-04 8:24 ` Amol Grover
2019-12-04 14:48 ` Jonathan Corbet
2019-12-04 15:39 ` Joel Fernandes
2019-12-04 15:47 ` Jonathan Corbet [this message]
2019-12-04 16:35 ` Joel Fernandes
2019-12-05 15:14 ` Amol Grover
2019-12-06 1:08 ` Joel Fernandes
2019-12-06 8:07 ` [PATCH v2] " Amol Grover
2019-12-19 16:29 ` Jonathan Corbet
2019-12-19 16:56 ` Paul E. McKenney
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=20191204084729.184480f3@lwn.net \
--to=corbet@lwn.net \
--cc=frextrite@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik04@gmail.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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).