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 720B12EBBB0; Thu, 17 Jul 2025 13:34:07 +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=1752759248; cv=none; b=MaYYkP6AhzO5CIQ1WBu5uIVVxVYXW1g2wSMP0trN921vTXF8md46nXmO+l3z50pHLE7tW8KA1urcVGGVpBxptk9I0TlzNQbSDlKTn6q1YfH0KDK2fm7NQv2b2lcWRuEJC+zKYvNVj05v13dDLwTz58R4+IL92QdQ1riELFdWX/4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752759248; c=relaxed/simple; bh=qyF6AcQjjMFZLje8IOQ87WS6iReSfovpUMWsJYjRghc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=A8D1VbCtM9n6kU86HmA5B1ZqKnxYo966vHcmTxUTA5GNDVNGs6jVThB/8aG3Ea8qcssL/gdSf22WIHpQEUS4qu8d7dJfTQkMy+hCJ62ODvImFaNHYy+HmLZakw15FZMPX7reokaAksGpv7jFCmfTEcbClKIx6DOk8rNdcLXaGMI= 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=JmDw+Dkj; 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="JmDw+Dkj" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 0181F403E1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1752759241; bh=kInJGEeRErYfW6zXowaP+WNNDVN8pRfm9KIQ0doInVM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=JmDw+DkjX2UBmvYwZDInKCYi2owhdRyxnfQXpuJXaM2KKN4H6RIzQvOOiH2ftAnJL 35IkpCeZhh0tiUZPi+WvleXpH+da/JEO4GDiZV9WglnUkkw3ztN8xNHvgmECEGO5pq COWv/MwFwjPRcUx/X2M7z3WgHdp5efeFVXtys2Wx7co9HNWnM31S8EFwZ3crUmhnMY luAWBR116LgkY+CiDnID5XIJ3y0gLO0KqfoCK7Y7ph6w6Xu3M3TDf/VHmwIbtSj5mQ UrREIZHeqwvQyBDKyz/1U40ydizTri1fGC4MB6fI31z80cqIBbiNo6WITsgQiXvMvl oxsfyBLHXqelw== 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 0181F403E1; Thu, 17 Jul 2025 13:34:01 +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: <20250717080617.35577-1-bagasdotme@gmail.com> References: <20250717080617.35577-1-bagasdotme@gmail.com> Date: Thu, 17 Jul 2025 07:34:00 -0600 Message-ID: <878qknc56f.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: kvm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain 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...? jon