From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kbuild@vger.kernel.org, kernel test robot <lkp@intel.com>,
Minchan Kim <minchan@kernel.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 08/14] zram: check that backends array has at least one backend
Date: Mon, 6 May 2024 15:43:35 +0900 [thread overview]
Message-ID: <20240506064335.GE8623@google.com> (raw)
In-Reply-To: <CAK7LNARUBuR3gDtX6GfB7Zv6dydt1+qzBB_XT58wOg3WeCTVvA@mail.gmail.com>
On (24/05/06 14:20), Masahiro Yamada wrote:
> config ZRAM_BACKEND_FORCE_LZO
> def_bool !ZRAM_BACKEND_LZ4 && !ZRAM_BACKEND_LZ4HC && \
> !ZRAM_BACKEND_ZSTD && !ZRAM_BACKEND_DEFLATE
>
> config ZRAM_BACKEND_LZO
> bool "lzo and lzo-rle compression support" if !ZRAM_BACKEND_FORCE_LZO
> depends on ZRAM
> default ZRAM_BACKEND_FORCE_LZO
> select LZO_COMPRESS
> select LZO_DECOMPRESS
I'll take this one. Thank you.
> BTW, "default n" you are adding are redundant.
OK.
next prev parent reply other threads:[~2024-05-06 6:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 9:17 [PATCH 00/14] zram: convert to custom comp API and allow algorithms configuration Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 01/14] zram: move from crypto API to custom comp backends API Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 02/14] zram: add lzo and lzorle compression backends support Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 03/14] zram: add lz4 compression backend support Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 04/14] zram: add lz4hc " Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 05/14] zram: add zstd " Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 06/14] zram: pass estimated src size hint to zstd Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 07/14] zram: add zlib compression backend support Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 08/14] zram: check that backends array has at least one backend Sergey Senozhatsky
2024-05-04 6:54 ` kernel test robot
2024-05-04 7:14 ` Sergey Senozhatsky
2024-05-04 23:10 ` Andrew Morton
2024-05-05 4:39 ` Sergey Senozhatsky
2024-05-05 5:13 ` Sergey Senozhatsky
2024-05-05 6:48 ` Sergey Senozhatsky
2024-05-06 3:22 ` Sergey Senozhatsky
2024-05-06 5:20 ` Masahiro Yamada
2024-05-06 6:43 ` Sergey Senozhatsky [this message]
2024-05-04 7:15 ` kernel test robot
2024-05-03 9:17 ` [PATCH 09/14] zram: introduce zcomp_config structure Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 10/14] zram: extend comp_algorithm attr write handling Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 11/14] zram: support compression level comp config Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 12/14] zram: add support for dict " Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 13/14] zram: add dictionary support to zstd backend Sergey Senozhatsky
2024-05-04 6:02 ` Sergey Senozhatsky
2024-05-03 9:17 ` [PATCH 14/14] Documentation/zram: add documentation for algorithm parameters Sergey Senozhatsky
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=20240506064335.GE8623@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=minchan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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