From: "honggyu.kim@sk.com" <honggyu.kim@sk.com>
To: "sj@kernel.org" <sj@kernel.org>
Cc: "damon@lists.linux.dev" <damon@lists.linux.dev>,
"hyeongtak.ji@sk.com" <hyeongtak.ji@sk.com>,
"byungchul@sk.com" <byungchul@sk.com>,
"hokyoon.lee@sk.com" <hokyoon.lee@sk.com>
Subject: Re: [PATCH] mm/damon/core.c: avoid unintentional filtering out of schemes
Date: Thu, 30 Nov 2023 06:37:29 +0000 [thread overview]
Message-ID: <1a2cc229c06c486db7177e12b5b4d601@sk.com> (raw)
Hi SeongJae,
>> Signed-off-by: Hyeongtak Ji <hyeongtak.ji@sk.com>
>
> Reviewed-by: SeongJae Park <sj@kernel.org>
Thanks for the review. I'm just sending this whether this message is correctly shown in LKML.
Thanks,
Honggyu
next reply other threads:[~2023-11-30 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 6:37 honggyu.kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-10 5:37 [PATCH] mm/damon/core.c: avoid unintentional filtering out of schemes Hyeongtak Ji
2023-11-10 18:22 ` SeongJae Park
2023-11-10 18:31 ` Andrew Morton
2023-11-11 0:34 ` Hyeongtak Ji
2023-11-10 18:31 ` SeongJae Park
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=1a2cc229c06c486db7177e12b5b4d601@sk.com \
--to=honggyu.kim@sk.com \
--cc=byungchul@sk.com \
--cc=damon@lists.linux.dev \
--cc=hokyoon.lee@sk.com \
--cc=hyeongtak.ji@sk.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).