linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
	honggyu.kim@sk.com, damon@lists.linux.dev, linux-mm@kvack.org,
	Alexandre Ghiti <alexghiti@rivosinc.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] selftests/damon: fix selftests by installing drgn related script
Date: Tue, 12 Aug 2025 19:45:56 -0700	[thread overview]
Message-ID: <20250813024556.52376-1-sj@kernel.org> (raw)
In-Reply-To: <CABFDxMF=-Fb56zSnGVvqXRrDXh-3vFzQmhuLNDYEzFv4z-bsuQ@mail.gmail.com>

On Wed, 13 Aug 2025 11:24:27 +0900 Sang-Heon Jeon <ekffu200098@gmail.com> wrote:

> Hi SeongJae
> 
> On Wed, Aug 13, 2025 at 2:59 AM SeongJae Park <sj@kernel.org> wrote:
> >
> > On Tue, 12 Aug 2025 23:00:46 +0900 Sang-Heon Jeon <ekffu200098@gmail.com> wrote:
[...]
> > > While setup kselftest executable environment and test this patch [1],
> > > I found similiar issue. Honestly, I don't know exact solution for this
> > > situation. So I just make a new patch. Sorry if it is wrong direction,
> > > then please let me know how to do next.
> > >
> > > [1] https://lore.kernel.org/damon/20250812-alex-fixes_manual-v1-1-c4e99b1f80e4@rivosinc.com/
> >
> > For patches that you are not really confident about and hence not insisting to
> > merge as-is, but wanna ask other's opinions first, you can ask questions via
> > plain text mails, or post patches with RFC tag on the subject.
> 
> My meaning of "don't know exact solution" was about conflict patch
> (Now I read again, I think other people might be confused.

Thank you for clarifying!

> That's you,
> sob) I will use the method mentioned above from now on.

In the case, another (and probably more common) approach would be sharing your
finding of remaining bugs with the original patch author.  Probably sharing
that as a reply-to-all to the patch would be good.  Then, the original author
could revise and post the next version of the patch in a more complete form.

[...]
> Thank you for this comment too, and for your always kindness.

The pleasure is mine :)


Thanks,
SJ

[...]


      reply	other threads:[~2025-08-13  2:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 14:00 Sang-Heon Jeon
2025-08-12 17:59 ` SeongJae Park
2025-08-12 22:17   ` Andrew Morton
2025-08-13  2:29     ` Sang-Heon Jeon
2025-08-13  2:24   ` Sang-Heon Jeon
2025-08-13  2:45     ` 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=20250813024556.52376-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexghiti@rivosinc.com \
    --cc=damon@lists.linux.dev \
    --cc=ekffu200098@gmail.com \
    --cc=honggyu.kim@sk.com \
    --cc=linux-mm@kvack.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