From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
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
Subject: Re: [PATCH 08/14] zram: check that backends array has at least one backend
Date: Sat, 4 May 2024 16:14:16 +0900 [thread overview]
Message-ID: <20240504071416.GH14947@google.com> (raw)
In-Reply-To: <202405041440.UTBQZAaf-lkp@intel.com>
On (24/05/04 14:54), kernel test robot wrote:
> | ~~~~~~~~~~~~~~~~~~~~~~
> >> drivers/block/zram/zcomp.c:214:2: error: call to '__compiletime_assert_285' declared with 'error' attribute: BUILD_BUG_ON failed: ARRAY_SIZE(backends) <= 1
> 214 | BUILD_BUG_ON(ARRAY_SIZE(backends) <= 1);
> | ^
So this is what that BUILD_BUG_ON() is supposed to catch. You don't
have any backends selected in your .config:
# CONFIG_ZRAM_BACKEND_LZO is not set
# CONFIG_ZRAM_BACKEND_LZ4 is not set
# CONFIG_ZRAM_BACKEND_LZ4HC is not set
# CONFIG_ZRAM_BACKEND_ZSTD is not set
# CONFIG_ZRAM_BACKEND_DEFLATE is not set
CONFIG_ZRAM_DEF_COMP="unset-value"
Which is invalid configuration because it means that zram has no
compression enabled.
next prev parent reply other threads:[~2024-05-04 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240503091823.3616962-9-senozhatsky@chromium.org>
2024-05-04 6:54 ` kernel test robot
2024-05-04 7:14 ` Sergey Senozhatsky [this message]
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
2024-05-04 7:15 ` kernel test robot
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=20240504071416.GH14947@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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