From: Mike Galbraith <efault@gmx.de>
To: "tiantao (H)" <tiantao6@huawei.com>,
Vitaly Wool <vitaly.wool@konsulko.com>,
Tian Tao <tiantao6@hisilicon.com>
Cc: Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
Andrew Morton <akpm@linux-foundation.org>,
Barry Song <song.bao.hua@hisilicon.com>,
Linux-MM <linux-mm@kvack.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [RFC mm/zswap 0/2] Fix the compatibility of zsmalloc and zswap
Date: Tue, 19 Jan 2021 03:39:16 +0100 [thread overview]
Message-ID: <286d155ac04eb2d5665d5c2b526edbcd34890547.camel@gmx.de> (raw)
In-Reply-To: <02c4d8df-da4f-e4b5-6a10-05e5f51ed6e7@huawei.com>
On Tue, 2021-01-19 at 09:31 +0800, tiantao (H) wrote:
>
> Is there anyone else testing this patch?
Dunno, but I'm not, Sebastian having already done that.
> Can I send an official patch out?
I don't see why not, it's been tested.
-Mike
next prev parent reply other threads:[~2021-01-19 2:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 11:02 [RFC mm/zswap 0/2] Fix the compatibility of zsmalloc and zswap Tian Tao
2020-12-25 11:02 ` [RFC mm/zswap 1/2] mm/zswap: add the flag can_sleep_mapped Tian Tao
2021-01-14 18:28 ` Minchan Kim
2021-01-14 18:40 ` Vitaly Wool
2021-01-14 18:56 ` Minchan Kim
2021-01-14 19:05 ` Vitaly Wool
2021-01-14 19:21 ` Shakeel Butt
2021-01-14 19:23 ` Minchan Kim
2021-01-14 19:53 ` Vitaly Wool
2021-01-14 21:09 ` Shakeel Butt
2021-01-14 22:41 ` Vitaly Wool
2021-01-19 1:28 ` tiantao (H)
2021-01-14 18:43 ` Shakeel Butt
2021-01-14 18:53 ` Vitaly Wool
2021-01-21 9:17 ` Vitaly Wool
2021-01-21 23:15 ` Song Bao Hua (Barry Song)
2020-12-25 11:02 ` [RFC mm/zswap 2/2] mm: set the sleep_mapped to true for zbud and z3fold Tian Tao
2021-01-14 18:46 ` [RFC mm/zswap 0/2] Fix the compatibility of zsmalloc and zswap Vitaly Wool
2021-01-15 1:17 ` tiantao (H)
2021-01-19 1:31 ` tiantao (H)
2021-01-19 2:39 ` Mike Galbraith [this message]
2021-01-18 13:44 ` Sebastian Andrzej Siewior
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=286d155ac04eb2d5665d5c2b526edbcd34890547.camel@gmx.de \
--to=efault@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=ddstreet@ieee.org \
--cc=linux-mm@kvack.org \
--cc=sjenning@redhat.com \
--cc=song.bao.hua@hisilicon.com \
--cc=tiantao6@hisilicon.com \
--cc=tiantao6@huawei.com \
--cc=vitaly.wool@konsulko.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 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.