Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp688829ybl; Wed, 4 Dec 2019 09:16:20 -0800 (PST) X-Google-Smtp-Source: APXvYqzvlweVkgk/YfewpdAVv40L8OSvKtAMC+nvojKGshHxAfdjHpcxGUOf1C/fOXygbvRbkkNY X-Received: by 2002:a9d:1425:: with SMTP id h34mr3303356oth.166.1575479779560; Wed, 04 Dec 2019 09:16:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575479779; cv=none; d=google.com; s=arc-20160816; b=la7nCj+ZtRYON/wo7RUJ0rIaaCXG29nIUTM1So8WtJFUO0P9hVdIzR2OLkMYJC5Fx3 lMu8hQeBLEC1Ygek/cx7eU2+5fCURW0qt3e1CsKWM0mOowJlAJVjGaES+UApgBlVRzt7 5+0egO9a63HKelLxxgy2x4JqZ0GwQsNz9Kekwrv/lRjIyuB3BDEqz9OikLo4C+rLlMZE oLl+WgzYbS5y2DplQFAJ3ecQslvQ9nYyApZYPR1Qzj0UhbHkQmDm/IUkPc/PsgUbmDgg 1KKuM5pGbVSXuatm5zYOvGfn+cNuNtLzPdYuHL2B/eh6TdhbT8VygGuDaxeC5Luy+RqP akkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=kyfsAzogiSLz59zOcDTZEK81sTsZ77EBTcEh25u2x+0=; b=qlDH/GONqEw40CjnMGbuN/2pbx0e9Li1H+N0lI4etoUNDr/jkaafIzp0qtN55BlK7i THBJSRuil3XRgt6sMHT/5pWLciFcEzTurmz1sJsLxihVgVA93V5x+StEbEW3mwl3aEij bm1y8OMcvRRiIGaR2sZC7Bqk27uy0v3ZLNjrmr4V6tovubIeerCJ5Eq+ymY99d7vIKS1 5uRJm8EAzAWs9UVSIOhfD1ZWe1QhUXaHZUtsZaXyl6aaiA20K0ZN9IJ55Eb2dwr/0HlU vLrNrFo842dZ9H98F9BqNvtWp+qNDYN89f3/DACt28fYX7pwSXxfh6c8gaAXuI0RpVxR GQgg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x21si3581140oif.250.2019.12.04.09.16.06; Wed, 04 Dec 2019 09:16:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728146AbfLDPrc (ORCPT + 99 others); Wed, 4 Dec 2019 10:47:32 -0500 Received: from ms.lwn.net ([45.79.88.28]:59874 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727878AbfLDPrb (ORCPT ); Wed, 4 Dec 2019 10:47:31 -0500 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 7F2D22D5; Wed, 4 Dec 2019 15:47:30 +0000 (UTC) Date: Wed, 4 Dec 2019 08:47:29 -0700 From: Jonathan Corbet To: Joel Fernandes Cc: Amol Grover , "Paul E . McKenney" , Josh Triplett , Steven Rostedt , Mathieu Desnoyers , Lai Jiangshan , rcu@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kernel-mentees@lists.linuxfoundation.org, Shuah Khan , Madhuparna Bhowmik Subject: Re: [PATCH] doc: listRCU: Add some more listRCU patterns in the kernel Message-ID: <20191204084729.184480f3@lwn.net> In-Reply-To: <20191204153958.GA17404@google.com> References: <20191203063941.6981-1-frextrite@gmail.com> <20191203064132.38d75348@lwn.net> <20191204082412.GA6959@workstation-kernel-dev> <20191204074833.44bcc079@lwn.net> <20191204153958.GA17404@google.com> Organization: LWN.net X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 4 Dec 2019 10:39:58 -0500 Joel Fernandes 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