From: SeongJae Park <sj@kernel.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
damon@lists.linux.dev
Subject: Re: [PATCH v3 0/3] mm/damon/paddr: minor code improvement
Date: Wed, 8 Mar 2023 18:17:17 +0000 [thread overview]
Message-ID: <20230308181717.46186-1-sj@kernel.org> (raw)
In-Reply-To: <20230308083311.120951-1-wangkefeng.wang@huawei.com>
Hi Kefeng,
On Wed, 8 Mar 2023 16:33:08 +0800 Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
> Unify folio_put() to make code more clear, and also fix minor issue in
> damon_pa_young().
>
> v3:
> - as SJ split the bugfix from v2, and it has merged[1], only do code
> improvement
> - fix a missing folio_sz update in damon_pa_young()
> - add RB from SJ
> - rebase on next-20230308
>
> [1] https://lkml.kernel.org/r/20230304193949.296391-1-sj@kernel.org
>
> v2:
> - use goto lable in damon_pa_pageout() and refact too more functions
>
> Kefeng Wang (3):
> mm/damon/paddr: minor refactor of damon_pa_pageout()
> mm/damon/paddr: minor refactor of
> damon_pa_mark_accessed_or_deactivate()
> mm/damon/paddr: fix missing folio_sz update in damon_pa_young()
>
> mm/damon/paddr.c | 26 ++++++++++----------------
> 1 file changed, 10 insertions(+), 16 deletions(-)
For the series,
Reviewed-by: SeongJae Park <sj@kernel.org>
Thank you for your efforts on this, Kefeng!
Thanks,
SJ
>
> --
> 2.35.3
>
prev parent reply other threads:[~2023-03-08 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 8:33 Kefeng Wang
2023-03-08 8:33 ` [PATCH v3 1/3] mm/damon/paddr: minor refactor of damon_pa_pageout() Kefeng Wang
2023-03-08 8:33 ` [PATCH v3 2/3] mm/damon/paddr: minor refactor of damon_pa_mark_accessed_or_deactivate() Kefeng Wang
2023-03-08 8:33 ` [PATCH v3 3/3] mm/damon/paddr: fix missing folio_sz update in damon_pa_young() Kefeng Wang
2023-03-08 18:17 ` 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=20230308181717.46186-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangkefeng.wang@huawei.com \
/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