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;
Subject: Re: drivers/remoteproc/st_remoteproc.c:114:20: sparse: sparse:
 incorrect type in argument 1 (different address spaces)
To:     Arnd Bergmann <arnd@arndb.de>, 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>
References: <202211091154.quYhgunB-lkp@intel.com>
 <5f51b4bd-3bc2-487b-aacd-9d0a1129c615@app.fastmail.com>
From:   "Chen, Rong A" <rong.a.chen@intel.com>
Message-ID: <1e65634e-9184-d93f-6477-bbe96193a5e3@intel.com>
Date:   Wed, 9 Nov 2022 15:57:17 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Firefox/78.0 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <5f51b4bd-3bc2-487b-aacd-9d0a1129c615@app.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 11/9/2022 3:33 PM, Arnd Bergmann wrote:
> 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.

Hi Arnd,

Thanks for your advice, we'll add the commit to ignore list.

Best Regards,
Rong Chen

> 
>> 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
>