From: SeongJae Park <sj@kernel.org>
To: mhocko@suse.com
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] Docs/mm/damon: Minor fixes and design doc update
Date: Fri, 26 May 2023 14:14:17 -0700 [thread overview]
Message-ID: <20230526211417.1902-1-sj@kernel.org> (raw)
In-Reply-To: <20230525214314.5204-1-sj@kernel.org>
On Thu, 25 May 2023 21:43:04 +0000 SeongJae Park <sj@kernel.org> wrote:
> Some of DAMON documents are outdated, or having minor typos or grammar
> erros. Especially, the design doc has not updated for DAMOS, which is
> an important part of DAMON. Fix the minor issues and update documents.
By the way, I started writing this patchset before LSFMM, but Michal's feedback
about DAMON documentation has definitely motivated this work, and was helpful.
Thank you, Michal. I just wanted to say that. Of course, more documentation
improvement works will be continued.
Thanks,
SJ
>
> SeongJae Park (10):
> Docs/mm/damon/faq: remove old questions
> Docs/mm/damon/maintainer-profile: fix typos and grammar errors
> Docs/mm/damon/design: add a section for overall architecture
> Docs/mm/damon/design: update the layout based on the layers
> Docs/mm/damon/design: rewrite configurable layers
> Docs/mm/damon/design: add a section for the relation between Core and
> Modules layer
> Docs/mm/damon/design: add sections for basic parts of DAMOS
> Docs/mm/damon/design: add sections for advanced features of DAMOS
> Docs/mm/damon/design: add a section for DAMON core API
> Docs/mm/damon/design: add a section for the modules layer
>
> Documentation/mm/damon/design.rst | 309 ++++++++++++++++--
> Documentation/mm/damon/faq.rst | 23 --
> Documentation/mm/damon/maintainer-profile.rst | 4 +-
> 3 files changed, 285 insertions(+), 51 deletions(-)
>
> --
> 2.25.1
>
prev parent reply other threads:[~2023-05-26 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 21:43 [PATCH 00/10] Docs/mm/damon: Minor fixes and design doc update SeongJae Park
2023-05-25 21:43 ` [PATCH 01/10] Docs/mm/damon/faq: remove old questions SeongJae Park
2023-05-25 21:43 ` [PATCH 02/10] Docs/mm/damon/maintainer-profile: fix typos and grammar errors SeongJae Park
2023-05-25 21:43 ` [PATCH 03/10] Docs/mm/damon/design: add a section for overall architecture SeongJae Park
2023-05-25 21:43 ` [PATCH 04/10] Docs/mm/damon/design: update the layout based on the layers SeongJae Park
2023-05-25 21:43 ` [PATCH 05/10] Docs/mm/damon/design: rewrite configurable layers SeongJae Park
2023-05-25 21:43 ` [PATCH 06/10] Docs/mm/damon/design: add a section for the relation between Core and Modules layer SeongJae Park
2023-05-25 21:43 ` [PATCH 07/10] Docs/mm/damon/design: add sections for basic parts of DAMOS SeongJae Park
2023-05-25 21:43 ` [PATCH 08/10] Docs/mm/damon/design: add sections for advanced features " SeongJae Park
2023-05-25 21:43 ` [PATCH 09/10] Docs/mm/damon/design: add a section for DAMON core API SeongJae Park
2023-05-25 21:43 ` [PATCH 10/10] Docs/mm/damon/design: add a section for the modules layer SeongJae Park
2023-05-26 21:14 ` SeongJae Park [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=20230526211417.1902-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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).