From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8CF8AC4332F for ; Wed, 9 Nov 2022 08:30:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230143AbiKIIaX (ORCPT ); Wed, 9 Nov 2022 03:30:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40340 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230051AbiKIIaH (ORCPT ); Wed, 9 Nov 2022 03:30:07 -0500 Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B1BB02229C; Wed, 9 Nov 2022 00:29:12 -0800 (PST) Received: by mail-pf1-x42e.google.com with SMTP id i3so16032266pfc.11; Wed, 09 Nov 2022 00:29:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=dHqVmoBRLCXyP1j0l5deF9pd4e0PRBaQAjJLi6rMh3Y=; b=bNYpd6fOAEPkFBgdNJfAnjfYOFgRecFDIVcFdbCB3kotZsewF4/r2mF3qVJN0EooBR 2g6EQbZnxLleP8zZ2wMl+8oZqcKRVzPhYMT0rAO5X+BXnh8GGgQD1PcZjYTmouSRWV+/ COYD+nyVEbl/88JLOpf5jkSagfnAnjIM9sN+/rlwobP0A7849CHePTt4Xd4qAWCp6NIT fRVP1knBiVFtDOWWKukUMdilAkeFlCShOlMClrPE8t8QgrqsCKURB2goXZQDSk8RCO9m MBsGxZ1Kzsou4CETTxjExpySKmu9ptlHul+y8MTWD19wNTu4GKeB1NzRDzF7Opb/3z1d Q+tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=dHqVmoBRLCXyP1j0l5deF9pd4e0PRBaQAjJLi6rMh3Y=; b=IyACUCvTvWK0CXxaCTnnynDV1tmoonTHtX2/cyrPjWJPYx7g2aTSycMF3TR5DonBSu BmenqPCTH5QTKJYTQsHhqEHwytLsH511o8AWyIBDEH+3EbhRvGvA48MuvlReR/VqAXEJ WQyA4H6kZ5yn3yboRW07hVFxQny4rrgEBGrkw3qy1wrIoX5xPXLP8Cu3s1Z3zcaXrq3V nABUi4e24MulQzMRDEJSHXpOPcMTaREpuWAsnGFTFCbi3ZFuxpAH8hgAg/QsYgkrgiUd 10qzvlO7kYaR3s30ToDPav/yJMxwSPdtj8aqrAvh6xeqGG8nw6hqEfseIiMgUMmGnjyv vGoA== X-Gm-Message-State: ACrzQf2pDJh+xzNsrmJDvSVntnYRAVqFULfcIM8/u/k+7VTRHK4+TqqJ vM3q8bfQhxUhIBfZ28cX1rbgg9lwFjX4xA== X-Google-Smtp-Source: AMsMyM4MyGSXc8iDU8z4fBb//Iy/GbYqIP0Xou51QXtMwzfDgIECKrQbjuGpptL8qpOK6Fh7cXGImA== X-Received: by 2002:a63:8449:0:b0:46e:ecba:c46d with SMTP id k70-20020a638449000000b0046eecbac46dmr52659709pgd.310.1667982549534; Wed, 09 Nov 2022 00:29:09 -0800 (PST) Received: from [192.168.43.80] (subs02-180-214-232-21.three.co.id. [180.214.232.21]) by smtp.gmail.com with ESMTPSA id b6-20020a170903228600b00186b0ac12c5sm8418374plh.172.2022.11.09.00.28.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 09 Nov 2022 00:29:09 -0800 (PST) Message-ID: <26188ff7-9a0c-d72c-b956-63d8f1c500ba@gmail.com> Date: Wed, 9 Nov 2022 15:28:54 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1 Subject: Re: [PATCH] Documentation: RCU: use code blocks with autogenerated line (was: Re: linux-next: build warning after merge of the rcu tree) Content-Language: en-US To: Akira Yokosawa Cc: corbet@lwn.net, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, paulmck@kernel.org, rcu@vger.kernel.org References: <206a95eb-5430-f9bf-15ad-4e644393255e@gmail.com> From: Bagas Sanjaya In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On 11/8/22 21:53, Akira Yokosawa wrote: >> I think only rcubarrier.rst have explicit references to line numbers. > > Oh, I find such references in (not limited to): > > - Documentation/RCU/Design/Requirements/Requirements.rst > - Documentation/RCU/Design/Data-Structures/Data-Structures.rst > Ah, I don't see these above! > Remember there is a note in Documentation/doc-guide/sphinx.rst > which reads: > > Please don't go overboard with reStructuredText markup. Keep it simple. > For the most part the documentation should be plain text with just enough > consistency in formatting that it can be converted to other formats. > > My interpretation of above: > > .rst sources should be kept as close to plain-text which can be > easily understood in dumb terminals, as far as possible. > Ah! I always forget that. I'm leaning towards *abusing* the markup, though. Thanks for the reminder. -- An old man doll... just what I always wanted! - Clara