[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191204163552.GE17404@google.com>
Date: Wed, 4 Dec 2019 11:35:52 -0500
From: Joel Fernandes <joel@...lfernandes.org>
To: Jonathan Corbet <corbet@....net>
Cc: Amol Grover <frextrite@...il.com>,
"Paul E . McKenney" <paulmck@...nel.org>,
Josh Triplett <josh@...htriplett.org>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <jiangshanlai@...il.com>, rcu@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org,
Shuah Khan <skhan@...uxfoundation.org>,
Madhuparna Bhowmik <madhuparnabhowmik04@...il.com>
Subject: Re: [PATCH] doc: listRCU: Add some more listRCU patterns in the
kernel
On Wed, Dec 04, 2019 at 08:47:29AM -0700, Jonathan Corbet wrote:
> On Wed, 4 Dec 2019 10:39:58 -0500
> Joel Fernandes <joel@...lfernandes.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.
I tried on a different machine (my work machine) and the cross-referencing is
working fine. So I am not sure if this could be something related to Sphinx
version or I had used an older kernel tree before. This kernel tree is
Linus's master.
thanks,
- Joel
Powered by blists - more mailing lists