From: Kees Cook <kees@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [kees:dev/next-20240618/kmem_buckets-v5 1/6] include/linux/slab.h:662:78: error: subscripted value is neither array nor pointer nor vector
Date: Thu, 20 Jun 2024 12:23:30 -0700 [thread overview]
Message-ID: <202406201222.BC51BD41@keescook> (raw)
In-Reply-To: <202406201723.BsMQJXcF-lkp@intel.com>
On Thu, Jun 20, 2024 at 05:21:23PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git dev/next-20240618/kmem_buckets-v5
> head: c823e15736071e9b694fc62be0c80cbda6a4e344
> commit: ac6eb1f5df288a356e73ab40d393a52cc2ec3ed1 [1/6] mm/slab: Introduce kmem_buckets typedef
> config: m68k-alldefconfig (https://download.01.org/0day-ci/archive/20240620/202406201723.BsMQJXcF-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240620/202406201723.BsMQJXcF-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/202406201723.BsMQJXcF-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> arch/m68k/include/asm/page.h:10:25: error: 'CONFIG_PAGE_SHIFT' undeclared here (not in a function); did you mean 'CONFIG_LOG_BUF_SHIFT'?
> 10 | #define PAGE_SHIFT CONFIG_PAGE_SHIFT
> | ^~~~~~~~~~~~~~~~~
This appears to be broken (-next?) build unrelated to the
kmem_buckets-v5 tree (when I revert all the changes the build still
fails).
--
Kees Cook
next prev parent reply other threads:[~2024-06-20 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 9:21 [kees:dev/next-20240618/kmem_buckets-v5 1/6] include/linux/slab.h:662:78: error: subscripted value is neither array nor pointer nor vector kernel test robot
2024-06-20 19:23 ` Kees Cook [this message]
2024-06-21 2:32 ` Philip Li
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=202406201222.BC51BD41@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.