From: Sang-Heon Jeon <ekffu200098@gmail.com>
To: SeongJae Park <sj@kernel.org>
Cc: honggyu.kim@sk.com, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH] selftests/damon: change wrong json.dump usage to json.dumps
Date: Sat, 16 Aug 2025 10:30:40 +0900 [thread overview]
Message-ID: <CABFDxMG+3trM45T_1L0_dv0ibQC2j_XXCeGEwY5RR8a8HZmoYQ@mail.gmail.com> (raw)
In-Reply-To: <20250815170948.16297-1-sj@kernel.org>
On Sat, Aug 16, 2025 at 2:09 AM SeongJae Park <sj@kernel.org> wrote:
>
> On Fri, 15 Aug 2025 18:40:29 +0900 Sang-Heon Jeon <ekffu200098@gmail.com> wrote:
>
> > To print drgn status to stdout json.dumps should be used without
> > json.dump. Change incorrect function call by typo.
> >
> > Fixes: 441f487d6ebf ("selftests/damon: test no-op commit broke DAMON status")
>
> Seems the fixee commit is on mm-unstable now. Since this commit ids on the
> tree is unreliable, I usually add a comment, like below.
>
> Fixes: 441f487d6ebf ("selftests/damon: test no-op commit broke DAMON status") # mm-unstable
I'll keep it my mind.
> Also, add the destination branch on patch subject prefix, like,
>
> [PATCH mm-unstable] selftests/damon: change wrong json.dump usage to json.dumps
>
> These are only my personal and undocumented conventions. I'm not sure if this
> helps others, but it would help me. Please consider using these conventions
> for DAMON patches in future. I'll document this on DAMON maintainer-profile
> document.
Sure, I'll follow your convention. Maybe If I don't follow, it just
means that I couldn't understand your comment and future document
well, haha.
> > Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
>
> Reviewed-by: SeongJae Park <sj@kernel.org>
>
> > ---
> > First I'm sorry that make you guys work twice. This is fix of my last
> > patch [1]. I'll be more careful next time.
> >
> > [1] https://lore.kernel.org/damon/20250810124354.16456-1-ekffu200098@gmail.com/
>
> Thank you for clarifying the context.
>
The pleasure is mine.
> Thanks,
> SJ
>
> [...]
Best Regards.
Sang-Heon Jeon
prev parent reply other threads:[~2025-08-16 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 9:40 Sang-Heon Jeon
2025-08-15 17:09 ` SeongJae Park
2025-08-16 1:30 ` Sang-Heon Jeon [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=CABFDxMG+3trM45T_1L0_dv0ibQC2j_XXCeGEwY5RR8a8HZmoYQ@mail.gmail.com \
--to=ekffu200098@gmail.com \
--cc=damon@lists.linux.dev \
--cc=honggyu.kim@sk.com \
--cc=linux-mm@kvack.org \
--cc=sj@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