[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <36cae99e-6a23-ab6f-62a7-5fca4ffc040d@canonical.com>
Date: Wed, 14 Apr 2021 17:17:41 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>,
kernel test robot <lkp@...el.com>
Cc: kbuild-all@...ts.01.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe_main.c:306:26:
sparse: sparse: incorrect type in argument 1 (different address spaces)
On 14/04/2021 16:53, Andy Shevchenko wrote:
> On Wed, Apr 14, 2021 at 10:21 AM kernel test robot <lkp@...el.com> wrote:
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: eebe426d32e1a10ac7c35f8ffab5f818c32a2454
>> commit: 8f28ca6bd8211214faf717677bbffe375c2a6072 iomap: constify ioreadX() iomem argument (as in generic implementation)
>> date: 8 months ago
>> config: alpha-randconfig-s032-20210414 (attached as .config)
>> compiler: alpha-linux-gcc (GCC) 9.3.0
>> reproduce:
>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> # apt-get install sparse
>> # sparse version: v0.6.3-280-g2cd6d34e-dirty
>> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f28ca6bd8211214faf717677bbffe375c2a6072
>> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> git fetch --no-tags linus master
>> git checkout 8f28ca6bd8211214faf717677bbffe375c2a6072
>> # save the attached .config to linux build tree
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=alpha
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@...el.com>
>
> I believe after my patch series [1] at least part of this will be
> gone. Can you confirm?
Have in mind that the warnings were there since beginning. My patch only
changed the warning contents (-> const) thus robot sees it as a new issue.
> [1]: https://lore.kernel.org/netdev/20210325173412.82911-1-andriy.shevchenko@linux.intel.com/T/#u
You convert the reg to "iomem", so it seems that yes, your series should
fix it.
Best regards,
Krzysztof
Powered by blists - more mailing lists