From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux RCU <rcu@vger.kernel.org>,
Linux CPU Architectures Development <linux-arch@vger.kernel.org>,
Linux LKMM <lkmm@lists.linux.dev>,
Linux KVM <kvm@vger.kernel.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
Alan Stern <stern@rowland.harvard.edu>,
Andrea Parri <parri.andrea@gmail.com>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
Mark Rutland <mark.rutland@arm.com>,
Ingo Molnar <mingo@redhat.com>, Waiman Long <longman@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Changyuan Lyu <changyuanl@google.com>,
Dan Williams <dan.j.williams@intel.com>,
Xavier <xavier_qy@163.com>, Randy Dunlap <rdunlap@infradead.org>,
Maarten Lankhorst <dev@lankhorst.se>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH 0/4] Convert atomic_*.txt and memory-barriers.txt to reST
Date: Thu, 17 Jul 2025 14:15:18 -0600 [thread overview]
Message-ID: <87freua815.fsf@trenco.lwn.net> (raw)
In-Reply-To: <878qknc56f.fsf@trenco.lwn.net>
Jonathan Corbet <corbet@lwn.net> writes:
> Bagas Sanjaya <bagasdotme@gmail.com> 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
prev parent reply other threads:[~2025-07-17 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 8:06 [PATCH 0/4] Convert atomic_*.txt and memory-barriers.txt to reST Bagas Sanjaya
2025-07-17 8:06 ` [PATCH 1/4] Documentation: memory-barriers: Convert to reST format Bagas Sanjaya
2025-07-17 8:06 ` [PATCH 2/4] Documentation: atomic_bitops: " Bagas Sanjaya
2025-07-17 8:06 ` [PATCH 3/4] Documentation: atomic_t: " Bagas Sanjaya
2025-07-17 8:06 ` [PATCH 4/4] Documentation: atomic_bitops, atomic_t, memory-barriers: Link to newly-converted docs Bagas Sanjaya
2025-07-17 10:55 ` [PATCH 0/4] Convert atomic_*.txt and memory-barriers.txt to reST Peter Zijlstra
2025-07-17 11:26 ` Bagas Sanjaya
2025-07-17 11:56 ` Vegard Nossum
2025-07-19 7:08 ` Bagas Sanjaya
2025-07-17 12:32 ` Steven Rostedt
2025-07-17 13:30 ` [PATCH 1/4] Documentation: memory-barriers: Convert to reST format David Howells
2025-07-17 13:34 ` [PATCH 0/4] Convert atomic_*.txt and memory-barriers.txt to reST Jonathan Corbet
2025-07-17 20:15 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87freua815.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=changyuanl@google.com \
--cc=dan.j.williams@intel.com \
--cc=dev@lankhorst.se \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=frederic@kernel.org \
--cc=j.alglave@ucl.ac.uk \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=luc.maranget@inria.fr \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--cc=will@kernel.org \
--cc=xavier_qy@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).