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 2/2] mm/../drivers/staging/android/ashmem.h:19:49: sparse: sparse: incorrect type in initializer (different base types)
Date: Tue, 31 Mar 2026 22:22:22 +0800 [thread overview]
Message-ID: <202603312223.BUJBFlUk-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18
head: 19c7b4b3480e0330addb0c3975aaf967070b2431
commit: 453cb76c605cfc3405a95bee4888782c7218b92a [2/2] ANDROID: mm/memfd-ashmem-shim: Align ioctl handler name with Rust version
config: arm-randconfig-r133-20260331 (https://download.01.org/0day-ci/archive/20260331/202603312223.BUJBFlUk-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260331/202603312223.BUJBFlUk-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/202603312223.BUJBFlUk-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
mm/shmem.c: note: in included file:
>> mm/../drivers/staging/android/ashmem.h:19:49: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted gfp_t static const [toplevel] [usertype] RUST_CONST_HELPER___GFP_FS @@ got unsigned long @@
mm/../drivers/staging/android/ashmem.h:19:49: sparse: expected restricted gfp_t static const [toplevel] [usertype] RUST_CONST_HELPER___GFP_FS
mm/../drivers/staging/android/ashmem.h:19:49: sparse: got unsigned long
>> mm/../drivers/staging/android/ashmem.h:20:49: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted gfp_t static const [toplevel] [usertype] RUST_CONST_HELPER___GFP_IO @@ got unsigned long @@
mm/../drivers/staging/android/ashmem.h:20:49: sparse: expected restricted gfp_t static const [toplevel] [usertype] RUST_CONST_HELPER___GFP_IO
mm/../drivers/staging/android/ashmem.h:20:49: sparse: got unsigned long
--
mm/memfd-ashmem-shim.c: note: in included file:
>> mm/../drivers/staging/android/ashmem.h:19:49: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted gfp_t static const [toplevel] [usertype] RUST_CONST_HELPER___GFP_FS @@ got unsigned long @@
mm/../drivers/staging/android/ashmem.h:19:49: sparse: expected restricted gfp_t static const [toplevel] [usertype] RUST_CONST_HELPER___GFP_FS
mm/../drivers/staging/android/ashmem.h:19:49: sparse: got unsigned long
>> mm/../drivers/staging/android/ashmem.h:20:49: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted gfp_t static const [toplevel] [usertype] RUST_CONST_HELPER___GFP_IO @@ got unsigned long @@
mm/../drivers/staging/android/ashmem.h:20:49: sparse: expected restricted gfp_t static const [toplevel] [usertype] RUST_CONST_HELPER___GFP_IO
mm/../drivers/staging/android/ashmem.h:20:49: sparse: got unsigned long
vim +19 mm/../drivers/staging/android/ashmem.h
17
18 #include <linux/shrinker.h>
> 19 static const gfp_t RUST_CONST_HELPER___GFP_FS = ___GFP_FS;
> 20 static const gfp_t RUST_CONST_HELPER___GFP_IO = ___GFP_IO;
21
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-31 14:22 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=202603312223.BUJBFlUk-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.