From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: "linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"naresh.kamboju@linaro.org" <naresh.kamboju@linaro.org>,
"pvorel@suse.cz" <pvorel@suse.cz>
Subject: Re: [PATCH v2 1/3] selftests/zram: Skip max_comp_streams interface on newer kernel
Date: Fri, 28 Jan 2022 01:17:22 +0000 [thread overview]
Message-ID: <61F3444C.9090000@fujitsu.com> (raw)
In-Reply-To: <c3410567-7d69-9020-8477-a8ba957505c8@linuxfoundation.org>
on 2022/1/28 2:05, Shuah Khan wrote:
> On 1/27/22 2:11 AM, Yang Xu wrote:
>> Since commit 43209ea2d17a ("zram: remove max_comp_streams internals"),
>> zram
>> has switched to per-cpu streams. Even kernel still keep this interface
>> for
>> some reasons, but writing to max_comp_stream doesn't take any effect. So
>> skip it on newer kernel ie 4.7.
>>
>> The code that comparing kernel version is from xfstests testsuite
>> ext4/053.
>>
>> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
>> ---
>
> Thank you. This and the other 2 patches are in linux-kselftest fixes branch
> for rc3.
Thanks for your review and merge.
Best Regards
Yang Xu
>
> thanks,
> -- Shuah
prev parent reply other threads:[~2022-01-28 1:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 9:56 [PATCH 1/3] selftests/zram: Remove obsolete max_comp_streams interface Yang Xu
2021-12-15 9:56 ` [PATCH 2/3] selftests/zram01.sh: Fix compression ratio calculation Yang Xu
2022-01-25 20:37 ` Shuah Khan
2022-01-26 6:08 ` xuyang2018.jy
2021-12-15 9:56 ` [PATCH 3/3] selftests/zram: Adapt the situation that /dev/zram0 is being used Yang Xu
2022-01-25 20:40 ` Shuah Khan
2022-01-13 6:26 ` [PATCH 1/3] selftests/zram: Remove obsolete max_comp_streams interface xuyang2018.jy
2022-01-25 20:52 ` Shuah Khan
2022-01-25 20:33 ` Shuah Khan
2022-01-26 5:19 ` xuyang2018.jy
2022-01-26 7:13 ` Petr Vorel
2022-01-26 17:35 ` Shuah Khan
2022-01-26 18:24 ` Petr Vorel
2022-01-26 18:37 ` Shuah Khan
2022-01-27 9:11 ` [PATCH v2 1/3] selftests/zram: Skip max_comp_streams interface on newer kernel Yang Xu
2022-01-27 9:11 ` [PATCH v2 2/3] selftests/zram01.sh: Fix compression ratio calculation Yang Xu
2022-01-27 9:11 ` [PATCH v2 3/3] selftests/zram: Adapt the situation that /dev/zram0 is being used Yang Xu
2022-01-27 18:05 ` [PATCH v2 1/3] selftests/zram: Skip max_comp_streams interface on newer kernel Shuah Khan
2022-01-28 1:17 ` xuyang2018.jy [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=61F3444C.9090000@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=pvorel@suse.cz \
--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).