From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Igor Belousov <igor.b@beldev.am>
Subject: [akpm-mm:mm-new 272/300] mm/zblock.h:24:2: warning: #warning This PAGE_SIZE is not quite supported yet
Date: Wed, 30 Apr 2025 15:10:30 +0800 [thread overview]
Message-ID: <202504301414.rk250nPa-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: f227084b1b7b3367578e989479a874af2c064c96
commit: 46ef148f198a9144df5e1ccf3a378d193c779f10 [272/300] mm-zblock-avoid-failing-the-build-fix
config: sparc64-randconfig-002-20250430 (https://download.01.org/0day-ci/archive/20250430/202504301414.rk250nPa-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250430/202504301414.rk250nPa-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/202504301414.rk250nPa-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from mm/zblock.c:28:
>> mm/zblock.h:24:2: warning: #warning This PAGE_SIZE is not quite supported yet [-Wcpp]
24 | #warning This PAGE_SIZE is not quite supported yet
| ^~~~~~~
vim +24 mm/zblock.h
16
17 #if PAGE_SIZE == 0x1000
18 /* max 128 slots per block, max table size 32 */
19 #define SLOT_BITS 7
20 #elif PAGE_SIZE == 0x4000
21 /* max 256 slots per block, max table size 64 */
22 #define SLOT_BITS 8
23 #else
> 24 #warning This PAGE_SIZE is not quite supported yet
25 #define SLOT_BITS 8
26 #endif
27
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-30 7:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202504301414.rk250nPa-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=igor.b@beldev.am \
--cc=linux-mm@kvack.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