Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-1115-g8b801eadce-fm-20221102.001-g8b801ead
Mime-Version: 1.0
Message-Id: <5f51b4bd-3bc2-487b-aacd-9d0a1129c615@app.fastmail.com>
In-Reply-To: <202211091154.quYhgunB-lkp@intel.com>
References: <202211091154.quYhgunB-lkp@intel.com>
Date:   Wed, 09 Nov 2022 08:33:30 +0100
From:   "Arnd Bergmann" <arnd@arndb.de>
To:     "kernel test robot" <lkp@intel.com>,
        "Kefeng Wang" <wangkefeng.wang@huawei.com>
Cc:     oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
        "Will Deacon" <will@kernel.org>, "Christoph Hellwig" <hch@lst.de>,
        "Russell King" <rmk+kernel@armlinux.org.uk>
Subject: Re: drivers/remoteproc/st_remoteproc.c:114:20: sparse: sparse: incorrect type
 in argument 1 (different address spaces)
Content-Type: text/plain
Precedence: bulk

On Wed, Nov 9, 2022, at 04:54, kernel test robot wrote:
> tree:   
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
> master
> head:   f141df371335645ce29a87d9683a3f79fba7fd67
> commit: d803336abdbc1bfacdb32b2cf9f4fdbee072b8ee ARM: mm: kill unused 
> runtime hook arch_iounmap()

Thanks for the report, but I think it might be better to stop
reporting address space violations from this patch, because it
only started showing existing known issues with a slightly
different error message, or flagging issues on arm32 that
were previously shown on other architectures.

> sparse warnings: (new ones prefixed by >>)
>    drivers/remoteproc/st_remoteproc.c:98:12: sparse: sparse: incorrect 
> type in assignment (different address spaces) @@     expected void *va 
> @@     got void [noderef] __iomem * @@
>    drivers/remoteproc/st_remoteproc.c:98:12: sparse:     expected void 
> *va
>    drivers/remoteproc/st_remoteproc.c:98:12: sparse:     got void 
> [noderef] __iomem *
>>> drivers/remoteproc/st_remoteproc.c:114:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *io_addr @@     got void *va @@

      Arnd