From: "liubo (AW)" <liubo254@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ying.huang@intel.com" <ying.huang@intel.com>,
"willy@infradead.org" <willy@infradead.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"surenb@google.com" <surenb@google.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"neilb@suse.de" <neilb@suse.de>,
"naoya.horiguchi@nec.com" <naoya.horiguchi@nec.com>,
"minchan@kernel.org" <minchan@kernel.org>,
linmiaohe <linmiaohe@huawei.com>,
Louhongxiang <louhongxiang@huawei.com>,
linfeilong <linfeilong@huawei.com>
Subject: Re: Re: [PATCH] mm/swapfile: release swap info when swap device is unpluged
Date: Wed, 15 Jun 2022 14:06:06 +0800 [thread overview]
Message-ID: <fd9e40a8-4782-a8ff-09d7-3c8f96c4bfb0@huawei.com> (raw)
In-Reply-To: <20220613144651.8f54b3da0c2e013d9db89f02@linux-foundation.org>
On 2022/6/14 5:46, Andrew Morton wrote:
> On Mon, 30 May 2022 13:00:24 +0000 "liubo (AW)" <liubo254@huawei.com> wrote:
>
>> friendly ping.
> I was hoping that someone might weigh in and review this, but no joy.
>
> The patch does quite a large amount of code movement, which makes it
> quite hard to review - to see what functionally changed. Is it possible to turn
> this into a two patch series? The first does the code movement with no
> functional changes and the second is the actual fix?
Thanks a lot for your comments, We'll do it in the next version.
prev parent reply other threads:[~2022-06-15 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 8:49 [PATCH] mm/swapfile: release swap info when swap device is unpluged liubo
2022-05-30 13:00 ` 答复: " liubo (AW)
2022-06-13 21:46 ` Andrew Morton
2022-06-15 6:06 ` liubo (AW) [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=fd9e40a8-4782-a8ff-09d7-3c8f96c4bfb0@huawei.com \
--to=liubo254@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linfeilong@huawei.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=louhongxiang@huawei.com \
--cc=minchan@kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=neilb@suse.de \
--cc=peterx@redhat.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).