From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-kminext 5/5] mm/mmzone.c:118:47: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Mon, 27 Jul 2026 20:08:58 +0800 [thread overview]
Message-ID: <202607271937.myLDNLMO-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18-kminext
head: 6ea6f1d2674f3ee03b932d9813dea9a0590e8a77
commit: aa2fcdf35fade78eec17bdfae208b652f11ab9a1 [5/5] ANDROID: mm: Create hooks for ZONE_MOVABLE allocs
config: i386-randconfig-r131-20260727 (https://download.01.org/0day-ci/archive/20260727/202607271937.myLDNLMO-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260727/202607271937.myLDNLMO-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/202607271937.myLDNLMO-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/mmzone.c:118:47: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int *flags @@ got restricted gfp_t * @@
mm/mmzone.c:118:47: sparse: expected unsigned int *flags
mm/mmzone.c:118:47: sparse: got restricted gfp_t *
--
>> mm/readahead.c:158:51: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int *flags @@ got restricted gfp_t * @@
mm/readahead.c:158:51: sparse: expected unsigned int *flags
mm/readahead.c:158:51: sparse: got restricted gfp_t *
vim +118 mm/mmzone.c
115
116 enum zone_type gfp_zone(gfp_t flags)
117 {
> 118 trace_android_rvh_set_gfp_zone_flags(&flags);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-27 12:09 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=202607271937.myLDNLMO-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.