From: SeongJae Park <sj@kernel.org>
To: KunWu Chan <kunwu.chan@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, corbet@lwn.net,
skhan@linuxfoundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Wang Lian <lianux.mm@gmail.com>
Subject: Re: [PATCH] Docs/damon: add TLB flush policy document
Date: Tue, 9 Jun 2026 07:28:21 -0700 [thread overview]
Message-ID: <20260609142823.68951-1-sj@kernel.org> (raw)
In-Reply-To: <CAN_Opa8sqs-V-jFrGZa6jwJKdHqT=7JPeLKcU8E-cCM74ON4DA@mail.gmail.com>
On Tue, 9 Jun 2026 16:11:30 +0800 KunWu Chan <kunwu.chan@gmail.com> wrote:
> On Sat, Jun 6, 2026 at 8:54 AM SeongJae Park <sj@kernel.org> wrote:
> >
> > Hi Kunwu and Lian,
> >
> > On Fri, 5 Jun 2026 11:10:08 +0800 Kunwu Chan <kunwu.chan@gmail.com> wrote:
[...]
> > Mainly due to the verbosity, as I above mentionedd, I'm not sure if the current
> > shape of this patch is the best to be merged as is. I also find the background
> > part of the document is a kind of duplicate of some information in design.rst.
> > What about putting only essential information in a condensed way on the
> > design.rst?
> >
> Thanks, SJ. I agree — this document reads more like an article than short docs.
>
> I'll follow your suggestion and submit it as a blog post to the DAMON
> project blog instead.
>
> Will send a PR to [2] soon. Thanks for the clear guidance.
Sounds good, looking forward to the PR!
>
> > [1] https://damonitor.github.io/site_about
> > [2] https://github.com/damonitor/damonitor.github.io/tree/master/blog_src
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-06-09 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 3:10 [PATCH] Docs/damon: add TLB flush policy document Kunwu Chan
2026-06-06 0:54 ` SeongJae Park
2026-06-09 8:11 ` KunWu Chan
2026-06-09 14:28 ` 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=20260609142823.68951-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=kunwu.chan@gmail.com \
--cc=liam@infradead.org \
--cc=lianux.mm@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.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