From: Andrew Morton <akpm@linux-foundation.org>
To: SeongJae Park <sj@kernel.org>
Cc: Gautam Menghani <gautammenghani201@gmail.com>,
skhan@linuxfoundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/damon : Add documentation for Enum value
Date: Tue, 10 May 2022 15:27:10 -0700 [thread overview]
Message-ID: <20220510152710.e112088bc5e4722e5cdad41c@linux-foundation.org> (raw)
In-Reply-To: <20220509081154.1834-1-sj@kernel.org>
On Mon, 9 May 2022 08:11:54 +0000 SeongJae Park <sj@kernel.org> wrote:
> I just found this patch is not cleanly applicable on top of the mm-unstable
> branch[1]. Could you please rebase?
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/log/?h=mm-unstable
I got it. It was just the DAMON_OPS_VADDR->DAMON_OPS_FVADDR rename.
prev parent reply other threads:[~2022-05-10 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 7:33 [PATCH] mm/damon : Add documentation for Enum value Gautam Menghani
2022-05-08 9:19 ` SeongJae Park
2022-05-09 8:11 ` SeongJae Park
2022-05-10 22:27 ` Andrew Morton [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=20220510152710.e112088bc5e4722e5cdad41c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gautammenghani201@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.org \
--cc=skhan@linuxfoundation.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 NNTP newsgroup(s).