From: SJ Park <sj@kernel.org>
To: Suhaas Joshi <suhaas@s-joshi.in>
Cc: SJ Park <sj@kernel.org>,
akpm@linux-foundation.org, aethernet65535@gmail.com,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm/damon/core: Use only installed probe in damon_merge_two_regions()
Date: Fri, 9 Oct 2026 00:46:10 -0700 [thread overview]
Message-ID: <20261009074611.40973-1-sj@kernel.org> (raw)
In-Reply-To: <ase2u791QTcV1LZt@fedora>
On Thu, 8 Oct 2026 21:03:15 +0530 Suhaas Joshi <suhaas@s-joshi.in> wrote:
> For some inexplicable reason, the cover-letter hasn't been sent again.
>
> I am just adding the changelog here, in case the cover letter never arrives.
>
> Changelog v1->v2:
>
> 1. Simplified patch 1's commit message to make it clearer
> (Liew's suggestion)
> 2. Added comment docs for extra arguments I am adding to functions
> (SJ's suggestion)
> 3. Destroyed the context in case r2 allocation fails in damon_test_merge_two()
> (Sashiko/Liew/SJ suggestion)
> 4. Wrapped lines at 80 characters
> (SJ's suggestion)
>
> As for why the cover-letter isn't being sent, I have no idea. Everything seems
> fine during `git send-email --dry-run`. Also seemed fine when I sent the series
> to myself as a test.
> Apologies for the inconvenience. I will make sure I fix this issue before sending
> v3 or any more series in the future.
No worries. Thank you for clarifying this! Maybe a possible workaround is
sending only cover letter first, confirming it is sent and appear on the
mailing list, and then sending patches using 'git send-email --in-reply-to'?
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-10-09 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261008151944.113714-1-suhaas@s-joshi.in>
2026-10-08 15:19 ` Suhaas Joshi
2026-10-08 15:33 ` Suhaas Joshi
2026-10-09 7:46 ` SJ Park [this message]
2026-10-09 7:43 ` SJ Park
2026-10-08 15:19 ` [PATCH v2 2/2] mm/damon/core: Copy only installed probe in damon_split_region_at() Suhaas Joshi
2026-10-09 2:40 ` kernel test robot
2026-10-09 8:21 ` SJ Park
2026-10-09 15:43 ` Suhaas Joshi
2026-10-09 4:06 ` kernel test robot
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=20261009074611.40973-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=suhaas@s-joshi.in \
/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
all inboxes | Powered by JetHome®