From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2D7E41F4CB2 for ; Thu, 17 Jul 2025 20:15:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.79.88.28 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752783321; cv=none; b=X/V1ksPzHcUjUOHrMfCPtvtPUquqN6Gk4nPJua3AV0qlbuL+BIIIgffJ0ZNfg4VnTk9HHacNDZKgHkP1iefyNcO3iKEBMFwjl3wRxDJguftAk5ouWyhhQvPTAOLJks7jgE2neARHvSrYQTJI7eP77JTNE0dwCACg/rosfV4aMW0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752783321; c=relaxed/simple; bh=orGo+e6PmYRc0yhWBvx1j4JissPIl+skfAa2q8N5kA0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=lwSJuI0uAhR+b6PT/HeVK5cilLlii/+FzBe/dF0qaMvIewnrp5VL7wCdmk8gxZ0LH8UsuTWJNi9TzdjkzvgtDJpeRRAz9/cMBPMpHci4V6l9iPnsHZyXBnaIxk9rksvMOo3ZYYNE1o2WBAAa+/aOfFJBHadTWP6sVJEumn9Qz1Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net; spf=pass smtp.mailfrom=lwn.net; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b=qYCc5Pq8; arc=none smtp.client-ip=45.79.88.28 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="qYCc5Pq8" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net EAA3C403E1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1752783319; bh=JyCg4buwTgeSf92B/ckI/zvTVv0LR8OvvXEMHW9FLS0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=qYCc5Pq80L6NNEBj2nIkMRSfXwRNZVFA142TIKS71oO93QeMrUiwUaGDZ/y7nfxfx +90gEWFUHF12P+VtJRq1VQ2M0/Oja9691zPeOzeF231p7EhN9jqjSl4ngmWxWAP1+3 FMGh3GIAtNSGzQDpkZEo0p88oolcTwiDszuxwRW8R0di9EOWUDPd7h7I0Z9oYPMY7n VK0T1VmZQCfIsfH2pQfbU1E19FiXStyvhtDqMYJlM9RjxTy/B6Lz8EUkgWe6xsMiHm Io5WHV/mpecywRV8aiQDXNeywsfh6aSr6nDggpO3XQMZBkz3k7UIl9q81huOsI+AxG E8tNUWD+HFvxQ== Received: from localhost (unknown [IPv6:2601:280:4600:2da9::1fe]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id EAA3C403E1; Thu, 17 Jul 2025 20:15:18 +0000 (UTC) From: Jonathan Corbet To: Bagas Sanjaya , Linux Kernel Mailing List , Linux Documentation , Linux RCU , Linux CPU Architectures Development , Linux LKMM , Linux KVM Cc: "Paul E. McKenney" , Frederic Weisbecker , Neeraj Upadhyay , Joel Fernandes , Josh Triplett , Boqun Feng , Uladzislau Rezki , Steven Rostedt , Mathieu Desnoyers , Lai Jiangshan , Zqiang , Alan Stern , Andrea Parri , Will Deacon , Peter Zijlstra , Nicholas Piggin , David Howells , Jade Alglave , Luc Maranget , Akira Yokosawa , Daniel Lustig , Mark Rutland , Ingo Molnar , Waiman Long , Paolo Bonzini , Bagas Sanjaya , Andrew Morton , Tejun Heo , "Mike Rapoport (Microsoft)" , Changyuan Lyu , Dan Williams , Xavier , Randy Dunlap , Maarten Lankhorst , Christian Brauner Subject: Re: [PATCH 0/4] Convert atomic_*.txt and memory-barriers.txt to reST In-Reply-To: <878qknc56f.fsf@trenco.lwn.net> References: <20250717080617.35577-1-bagasdotme@gmail.com> <878qknc56f.fsf@trenco.lwn.net> Date: Thu, 17 Jul 2025 14:15:18 -0600 Message-ID: <87freua815.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: lkmm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Jonathan Corbet writes: > Bagas Sanjaya writes: > >> Atomic types, atomic bitops, and memory barriers docs are included in kernel >> docs build since commit e40573a43d163a ("docs: put atomic*.txt and >> memory-barriers.txt into the core-api book") as a wrapper stub for >> corresponding uncoverted txt docs. Let's turn them into full-fledged reST docs. > > Did it occur to you to look at the changelog for the commit you cite, > which explains why those documents are handled the way they are...? I'm sorry, that caught me at the wrong time, and I was rather more harsh than I should have been. I should not have responded that way. For future reference, though, when somebody has gone out of their way to accomplish a task in a specific way, there usually *is* a reason for it. If you can't find that reason, the best thing to do is usually to ask. Thanks, jon