From: Jonathan Corbet <corbet@lwn.net>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/admin-guide/mm: add high level concepts overview
Date: Tue, 29 May 2018 06:21:31 -0600 [thread overview]
Message-ID: <20180529062131.545d4e34@lwn.net> (raw)
In-Reply-To: <20180529113725.GB13092@rapoport-lnx>
On Tue, 29 May 2018 14:37:25 +0300
Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> The are terms that seem obvious to the mm developers, but may be somewhat
> obscure for, say, less involved readers.
>
> The concepts overview can be seen as an "extended glossary" that introduces
> such terms to the readers of the kernel documentation.
So as I read through this I thought of all kinds of ways it could be
improved, but I suspect that will always be the case. It's a good intro
as-is, so I've applied it. Thanks!
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/admin-guide/mm: add high level concepts overview
Date: Tue, 29 May 2018 06:21:31 -0600 [thread overview]
Message-ID: <20180529062131.545d4e34@lwn.net> (raw)
In-Reply-To: <20180529113725.GB13092@rapoport-lnx>
On Tue, 29 May 2018 14:37:25 +0300
Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> The are terms that seem obvious to the mm developers, but may be somewhat
> obscure for, say, less involved readers.
>
> The concepts overview can be seen as an "extended glossary" that introduces
> such terms to the readers of the kernel documentation.
So as I read through this I thought of all kinds of ways it could be
improved, but I suspect that will always be the case. It's a good intro
as-is, so I've applied it. Thanks!
jon
next prev parent reply other threads:[~2018-05-29 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 11:37 [PATCH] docs/admin-guide/mm: add high level concepts overview Mike Rapoport
2018-05-29 11:37 ` Mike Rapoport
2018-05-29 11:37 ` Mike Rapoport
2018-05-29 12:18 ` Justin Skists
2018-05-29 12:18 ` Justin Skists
2018-05-29 12:21 ` Jonathan Corbet [this message]
2018-05-29 12:21 ` Jonathan Corbet
2018-06-02 0:09 ` Randy Dunlap
2018-06-02 0:09 ` Randy Dunlap
2018-06-04 12:22 ` Mike Rapoport
2018-06-04 12:22 ` Mike Rapoport
2018-06-04 12:22 ` Mike Rapoport
2018-06-04 15:53 ` Randy Dunlap
2018-06-04 15:53 ` Randy Dunlap
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=20180529062131.545d4e34@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.