[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230801095321.3ce734c1@kernel.org>
Date: Tue, 1 Aug 2023 09:53:21 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: kernel test robot <lkp@...el.com>, <oe-kbuild-all@...ts.linux.dev>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
loongarch@...ts.linux.dev
Subject: Re: [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9:
sparse: sparse: incorrect type in argument 1 (different address spaces)
On Tue, 1 Aug 2023 15:46:22 +0200 Alexander Lobakin wrote:
> > 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@...el.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202307292029.cFz0s8Hh-lkp@intel.com/
>
> Jakub, could you take a look, is this warning reasonable?
Doesn't look legit to me. I can't repro it on x86 and:
$ head .config
#
# Automatically generated file; DO NOT EDIT.
# Linux/loongarch 6.5.0-rc3 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="loongarch64-linux-gcc (GCC) 12.3.0"
Adding loongarch to CC, it must be arch specific ?
Powered by blists - more mailing lists