From: Linus Walleij <linus.walleij@linaro.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v5] Documentation/mm: Initial page table documentation
Date: Wed, 21 Jun 2023 09:35:29 +0200 [thread overview]
Message-ID: <CACRpkdbGfVvFtTA_tcSsmj_1t6aiwPfzYp07UC1NSfSMBVYE+A@mail.gmail.com> (raw)
In-Reply-To: <13291493.dW097sEU6C@suse>
Hi Fabio!
thanks for your reply!
The ways of technical documentation are never easy, but what
we are using right now is the socratic method, dialogue at its best,
which is pretty much the best way I know.
WRT the problem of education:
In gloomy days I have been referring to something I tongue-in-cheek
call "the second software crisis" (not any established term)
so in contrast with the first software crisis which was about the
complexity of software development outgrowing hardware
development, the second software crisis is due to software
developers losing contact and knowledge of hardware, with big
white spots on their mental map so that is part of what I am
trying to fix here.
Best regards,
Linus Walleij
prev parent reply other threads:[~2023-06-21 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 7:25 Linus Walleij
2023-06-16 14:14 ` Jonathan Corbet
2023-06-18 13:16 ` Fabio M. De Francesco
2023-06-18 18:54 ` Jonathan Corbet
2023-06-19 8:16 ` Linus Walleij
2023-06-21 1:10 ` Fabio M. De Francesco
2023-06-21 7:35 ` Linus Walleij [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=CACRpkdbGfVvFtTA_tcSsmj_1t6aiwPfzYp07UC1NSfSMBVYE+A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=fmdefrancesco@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=willy@infradead.org \
/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