Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp781229ybc; Tue, 12 Nov 2019 09:06:16 -0800 (PST) X-Google-Smtp-Source: APXvYqwSPV/t32URA7QiQ5+dDrGIuhwYUem5pwcY+53xKcLSzEe9l++c4iGJlqEIf3cWASNHkiLY X-Received: by 2002:adf:e28f:: with SMTP id v15mr25830091wri.130.1573578375870; Tue, 12 Nov 2019 09:06:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573578375; cv=none; d=google.com; s=arc-20160816; b=fpba4sp6scOEXov7MuVeEvdqSmqcKBlXsd/0Od4ebSfVX+9V/cl27gbDC1BQROocne rq2SeM8UK/N0dfSTAyeLa5bJ+hkTy6Vc1M6mB1OKFO90qskIJE4TM5ewBMmMYaD9CIlr YrrJ3jPOHbmgCZ+NYl2kV4Nom6PaZePQEJxGxW7RL7cGqffcD/Kgu0fvQ0mTOGUHdpWH G3ISlsBa9AFbqE4J2VhQbw0X2JBFqchk4XtBA8U4IGayQ9lu9spGHQ6e4DU+sopYvsCZ AEbSajQ1VZyLO+kTOux32uItPK8kH+x2bM71IL8lEJLboYECJjzuMZ0KWVJrEZXaTUdS sbDg== 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=sRvIIWKsM2gvCw5ErUN8MkUnCKHM338Mh60qWd9qsPU=; b=VjE8RvfoYEozYenj4yJYlkVZbzbFMpiqSienZ9M12su1lGh0LWn9nDccAhC3Doo11m NLu2yt2BQaKJ73ebZrtD1UTyCsDd6An+g10PcygPbhZWuf1vZiYn8aJXLU6RkTPxPiXp BbJFdeokm+2+K4b35JTsNvmraT8RwBQCmUDAA2Qg57dVy1Johk2q/oOSS8hg0H4UWrhs aV7v0AYstova/q2THK7M/S01kgHuRP31KENvKyE7aBav7l+8KhUQNby9ZZmskO02oaol oIFiYKsuf9G/Iy2qXMkKbAw8PcoNsrVdwyWzllDOL0fluv8N8CCJe1rXTuGrMBNKoPh6 FDbg== 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 y32si14276770ede.209.2019.11.12.09.05.38; Tue, 12 Nov 2019 09:06:15 -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 S1726958AbfKLRE7 (ORCPT + 99 others); Tue, 12 Nov 2019 12:04:59 -0500 Received: from ms.lwn.net ([45.79.88.28]:42024 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726718AbfKLRE6 (ORCPT ); Tue, 12 Nov 2019 12:04:58 -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 BFF415A0; Tue, 12 Nov 2019 17:04:56 +0000 (UTC) Date: Tue, 12 Nov 2019 10:04:54 -0700 From: Jonathan Corbet To: Jaskaran Singh Cc: linux-kernel@vger.kernel.org, mchehab+samsung@kernel.org, christian@brauner.io, neilb@suse.com, willy@infradead.org, tobin@kernel.org, stefanha@redhat.com, hofrat@osadl.org, gregkh@linuxfoundation.org, jeffrey.t.kirsher@intel.com, linux-doc@vger.kernel.org, skhan@linuxfoundation.org, "linux-kernel-mentees@lists.linuxfoundation.org" Subject: Re: [PATCH][RESEND] docs: filesystems: sysfs: convert sysfs.txt to reST Message-ID: <20191112100454.3b41f3af@lwn.net> In-Reply-To: References: <20191105071846.GA28727@localhost.localdomain> <20191107120455.29a4c155@lwn.net> 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 Sat, 09 Nov 2019 18:36:16 +0530 Jaskaran Singh wrote: > > At a bare minimum, an effort like this needs to put a big flashing > > warning > > at the top of the file. But it would be soooooo much better to > > actually > > update the content as well. > > > > The best way to do that would be to annotate the source with proper > > kerneldoc comments, then pull them into the documentation rather than > > repeating the information here. Is there any chance you might be up > > for > > taking on a task like this? > > > > > Sure! I'll send the documentation patch(es) followed by a v2 for this > patch. Great. As an alternative, if you like, redo the current patch with the other suggested fixes and a "this is obsolete" warning at the top. Then, after the subsequent improvements land, that warning can eventually be removed again. Thanks, jon