All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Aveline Noir <jm5905938@gmail.com>
Cc: SJ Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	damon@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
	sashiko-bot@kernel.org, sashiko-reviews@lists.linux.dev,
	Shuah Khan <shuah@kernel.org>,
	stable@vger.kernel.org
Subject: Re: [RFC PATCH] selftests/damon/sysfs_memcg_path_leak: define ksft_skip
Date: Sat, 31 Oct 2026 10:47:25 -0700	[thread overview]
Message-ID: <20261031174726.85433-1-sj@kernel.org> (raw)
In-Reply-To: <179346448183.4.15545164251841296990@gmail.com>

On Sun, 01 Nov 2026 03:34:41 +1100 Aveline Noir <jm5905938@gmail.com> wrote:

> Hi SJ,
> 
> On Sat, 31 Oct 2026 08:38:58 -0700 SJ Park wrote:
> 
> > Thank you for reviewing, Aveline.
> 
> Oh, looks like I forgot that. Thanks for the reminder.

No worries!

> 
> That also gives me an idea: maybe I could build a modular tool to help
> write emails. Building on b4 might be a good starting point.

Sounds like a good plan!

> 
> Tested the non-root skip path on x86-64 Linux with Bash 5.3.20:
> the exit status changed from 0 to 4.
> 
> Reviewed-by: Aveline Noir <jm5905938@gmail.com>
> Tested-by: Aveline Noir <jm5905938@gmail.com>

Thank you for reviewing and testing!


Thanks,
SJ

[...]

      reply	other threads:[~2026-10-31 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  4:46 [RFC PATCH] selftests/damon/sysfs_memcg_path_leak: define ksft_skip SJ Park
2026-10-30  4:48 ` sashiko-bot
2026-10-31  4:36 ` Aveline Noir
2026-10-31 15:38   ` SJ Park
2026-10-31 16:34     ` Aveline Noir
2026-10-31 17:47       ` 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=20261031174726.85433-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=jm5905938@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=shuah@kernel.org \
    --cc=stable@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 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.