From: SeongJae Park <sj@kernel.org>
To: Aether <aethernet65535@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation/mm/damon: fix typo in index.rst
Date: Sun, 8 Mar 2026 10:14:31 -0700 [thread overview]
Message-ID: <20260308171432.209411-1-sj@kernel.org> (raw)
In-Reply-To: <CAPLv50pFasDAnFMX8OgXjo2Nrn8rGhUgm1=K5aOeVyKf57Z3BQ@mail.gmail.com>
Hi Liew Rui Yan,
On Sun, 8 Mar 2026 11:05:09 +0800 Aether <aethernet65535@gmail.com> wrote:
> Hi SeongJae,
>
> I just noticed that you already submitted the same fix for the type in
> Documentation/mm/damon/index.rst.
Yes, I unfortunately sent [1] it a few hours before your posting.
> Sorry for the duplicate!
No worry, this kind of duplication is very common in our real life! I'm rather
sorry that I wasted your time by posting my patch too late.
>
> I'll make sure to search the mailing list first next time before submitting a
> patch.
Such searching would be exhausting. Please feel free to just send patches. I
can help handling such duplications :)
Nonetheless, if you really want to avoid this kind of duplication, checking
damon/next tree [2] before starting your work could be a good practice. The
tree contains all DAMON patches that aimed to be mainlined in near future.
Note that the tree also contains patches that not aim to be mainlined in near
future. If you get any question about the tree, please feel free to reach out
to me.
> Thanks for the quick fix, and thanks for maintaining DAMON!
My greatest pleasure!
[1] https://lore.kernel.org/20260307195356.203753-8-sj@kernel.org
[2] https://origin.kernel.org/doc/html/latest/mm/damon/maintainer-profile.html#scm-trees
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-03-08 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 2:18 [PATCH] Documentation/mm/damon: fix typo in index.rst aethernet
2026-03-08 3:05 ` Aether
2026-03-08 17: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=20260308171432.209411-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--cc=linux-doc@vger.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