All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Manuel Ebner <manuelebnerli@mailbox.org>
Cc: SJ Park <sj@kernel.org>,
	damon@lists.linux.dev, Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-mm@kvack.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Aveline Noir <jm5905938@gmail.com>,
	"Adrian Huang (Lenovo)" <adrianhuang0701@gmail.com>
Subject: Re: [Duplicate Text] in mm/damon/ and Doc/admin-guide/mm/damon/
Date: Sat, 17 Oct 2026 09:29:53 -0700	[thread overview]
Message-ID: <20261017162954.104148-1-sj@kernel.org> (raw)
In-Reply-To: <1061edcf257c9e625efe5f6f000013e9b2d4c650.camel@mailbox.org>

On Sat, 17 Oct 2026 17:32:47 +0200 Manuel Ebner <manuelebnerli@mailbox.org> wrote:

> Hi SJ,
> 
> there is a lot of duplicated text in these directories. Diff doesn't show
> any because in mm/damon/ the text is a multi-line comment.
> 
> ~40 Lines in lru_sort.c and lru_sort.rst,
> ~50 Lines in reclaim.c and reclaim.rst and
> a few Lines in stat.c and stat.rst.
> 
> I think it's important to decide on how to handle the duplication before
> patching.
> 
> Delete one set, keep (and fix) both or add a reference in one place to
> the other? Could sphinx do the duplication?

Let's keep and fix both for now.  We can consider deduplicating if it turns out
to be too much overhead.  I don't feel so yet.


Thanks,
SJ

[...]


      reply	other threads:[~2026-10-17 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 15:32 [Duplicate Text] in mm/damon/ and Doc/admin-guide/mm/damon/ Manuel Ebner
2026-10-17 16:29 ` SJ 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=20261017162954.104148-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=adrianhuang0701@gmail.com \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=jm5905938@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=manuelebnerli@mailbox.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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 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.