From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: "Byungchul Park" <byungchul@sk.com>,
oe-kbuild-all@lists.linux.dev,
"David Hildenbrand" <david@kernel.org>,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Pavel Begunkov" <asml.silence@gmail.com>,
" Toke Høiland-Jørgensen " <toke@redhat.com>
Subject: Re: [akpm-mm:mm-unstable /301] net/core/page_pool.c:713:71: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Fri, 16 Jan 2026 15:15:00 -0800 [thread overview]
Message-ID: <20260116151500.b56d0cc2525072123ad2d86d@linux-foundation.org> (raw)
In-Reply-To: <202601161606.8RuyUh2k-lkp@intel.com>
On Fri, 16 Jan 2026 16:41:32 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head: fe2c34b6ea5a0e1175c30d59bc1c28caafb02c62
> commit: 7699fe82442a62ea29a3745b29dbb8ef8c42d8db [/301] mm: introduce a new page type for page pool in page type
> config: x86_64-randconfig-122-20260115 (https://download.01.org/0day-ci/archive/20260116/202601161606.8RuyUh2k-lkp@intel.com/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260116/202601161606.8RuyUh2k-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/202601161606.8RuyUh2k-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> net/core/page_pool.c:713:71: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted netmem_ref [usertype] netmem @@ got unsigned long @@
> net/core/page_pool.c:713:71: sparse: expected restricted netmem_ref [usertype] netmem
> net/core/page_pool.c:713:71: sparse: got unsigned long
> net/core/page_pool.c:734:73: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted netmem_ref [usertype] netmem @@ got unsigned long @@
> net/core/page_pool.c:734:73: sparse: expected restricted netmem_ref [usertype] netmem
> net/core/page_pool.c:734:73: sparse: got unsigned long
Oh, OK.
Byungchul, please remind me why I'm carrying a page-pool patch? I
applied it because email headers and because Suggested-by:David, but
these things are usually carried in the networking tree.
And I never applied [patch 2/2]
(https://lkml.kernel.org/r/20251215071001.78263-3-byungchul@sk.com)
because "kernel test robot" reported a build error.
In fact, I'll drop the patch - please let's have a redo.
next prev parent reply other threads:[~2026-01-16 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 8:41 kernel test robot
2026-01-16 23:15 ` Andrew Morton [this message]
2026-01-26 9:16 ` Byungchul Park
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=20260116151500.b56d0cc2525072123ad2d86d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=asml.silence@gmail.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=toke@redhat.com \
/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