From: Jakub Kicinski <kuba@kernel.org>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
loongarch@lists.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)
Date: Tue, 1 Aug 2023 09:53:21 -0700 [thread overview]
Message-ID: <20230801095321.3ce734c1@kernel.org> (raw)
In-Reply-To: <217dc739-05f5-a708-d358-ba331325d0cd@intel.com>
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@intel.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 ?
next prev parent reply other threads:[~2023-08-01 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202307292029.cFz0s8Hh-lkp@intel.com>
2023-08-01 13:46 ` [alobakin:iavf-pp-frag 11/28] net/core/page_pool.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) Alexander Lobakin
2023-08-01 16:53 ` Jakub Kicinski [this message]
2023-08-01 17:03 ` Alexander Lobakin
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=20230801095321.3ce734c1@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=lkp@intel.com \
--cc=loongarch@lists.linux.dev \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).