From: Kees Cook <kees@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [kees:for-next/kspp 17/18] include/linux/compiler_types.h:572:45: error: call to '__compiletime_assert_246' declared with attribute error: BUILD_BUG_ON failed: init___fls < 32
Date: Wed, 3 Sep 2025 20:54:18 -0700 [thread overview]
Message-ID: <202509032053.EDA3CC3CF5@keescook> (raw)
In-Reply-To: <202509011237.Hf8MjkXU-lkp@intel.com>
On Mon, Sep 01, 2025 at 12:49:17PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/kspp
> head: 6a38fe1a7d9c9eba3330a8ae4ece2fa5d0f628cc
> commit: 159746fccb2e000bbac46fe24034d38e7df6c6e2 [17/18] KUnit: ffs: Validate all the __attribute_const__ annotations
> config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20250901/202509011237.Hf8MjkXU-lkp@intel.com/config)
> compiler: arc-linux-gcc (GCC) 15.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250901/202509011237.Hf8MjkXU-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202509011237.Hf8MjkXU-lkp@intel.com/
This should be fixed now:
https://lore.kernel.org/all/20250831022352.it.055-kees@kernel.org/
Thanks!
-Kees
--
Kees Cook
prev parent reply other threads:[~2025-09-04 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 4:49 [kees:for-next/kspp 17/18] include/linux/compiler_types.h:572:45: error: call to '__compiletime_assert_246' declared with attribute error: BUILD_BUG_ON failed: init___fls < 32 kernel test robot
2025-09-04 3:54 ` Kees Cook [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=202509032053.EDA3CC3CF5@keescook \
--to=kees@kernel.org \
--cc=lkp@intel.com \
--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 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.