public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Ignacio Encinas Rubio <ignacio@iencinas.com>
To: lkmm@lists.linux.dev
Cc: mchehab+huawei@kernel.org, paulmck@kernel.org,
	joel@joelfernandes.org, Akira Yokosawa <akiyks@gmail.com>,
	linux-kernel-mentees@lists.linux.dev, peterz@infradead.org,
	stern@rowland.harvard.edu, corbet@lwn.net,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Potential translation of LKMM docs into ReST
Date: Sun, 30 Mar 2025 13:07:23 +0200	[thread overview]
Message-ID: <837b4d83-b91f-40d1-995a-aa3c5a925b0b@iencinas.com> (raw)

Hello!

There is interest [1] to get the memory model documentation into the 
built docs. Akira pointed out that this was discussed in the past [2].

A couple of years have gone by, so I was wondering whether the decision
to keep plain text documentation still applies. 

There is an "easy" way [3] to get the plain text documentation into the
built docs, but I would be happy to work in a conversion into ReST if
that's what you want :)

Ccing people involved in [2]

Thanks!

[1] https://lore.kernel.org/all/87o6y5lvvg.fsf@trenco.lwn.net/
[2] https://lore.kernel.org/lkml/20190901133530.GL4125@linux.ibm.com/
[3] https://lore.kernel.org/all/20220927160559.97154-7-corbet@lwn.net/

             reply	other threads:[~2025-03-30 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-30 11:07 Ignacio Encinas Rubio [this message]
2025-03-30 16:09 ` Potential translation of LKMM docs into ReST Alan Stern
2025-03-30 17:52   ` Mauro Carvalho Chehab
2025-05-06  2:50 ` [PATCH] lkmm: docs: Put LKMM documentation into dev-tools book Akira Yokosawa
2025-05-07  0:07   ` Paul E. McKenney
2025-06-09 22:03   ` Jonathan Corbet
2025-06-10  2:11     ` Akira Yokosawa
2025-06-10  8:13       ` Mauro Carvalho Chehab

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=837b4d83-b91f-40d1-995a-aa3c5a925b0b@iencinas.com \
    --to=ignacio@iencinas.com \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=lkmm@lists.linux.dev \
    --cc=mchehab+huawei@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=stern@rowland.harvard.edu \
    /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