Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 18 Jun 2020 20:55:07 +0200
From:   Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     kernel test robot <lkp@intel.com>, kbuild-all@lists.01.org,
        LKML <linux-kernel@vger.kernel.org>,
        Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Subject: Re: [PATCH] sparse: use identifiers to define address spaces
Message-ID: <20200618185507.p5tmurllwygmfwrq@ltop.local>
References: <20200617220226.88948-1-luc.vanoostenryck@gmail.com>
 <202006181747.1x7hGaZR%lkp@intel.com>
 <CAHk-=wi=y6XoZKjxoGf9h4Zj3SPZnA+g5ZjsZ2hKT-AZW7H0ag@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHk-=wi=y6XoZKjxoGf9h4Zj3SPZnA+g5ZjsZ2hKT-AZW7H0ag@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Jun 18, 2020 at 09:59:05AM -0700, Linus Torvalds wrote:
> 
> The new warnings don't seem to be due to the kernel test robot having
> an old version of sparse, but just because the error strings changed,
> and presumably the kernel test robot has some "ignore old sparse
> warnings" logic.
> 
> So the warnings all look new, even if they aren't.

What is strange is that only some of these warnings are shown as
new, but not all.  For example it shows
  >> drivers/spi/spi-fsl-spi.c:93:44: sparse:     got void [noderef] __iomem *reg_base

as new, but not the following one:
  drivers/spi/spi-fsl-spi.c:294:44: sparse:     got void [noderef] __iomem *reg_base

while both have their string changed (__iomem).

Just to be sure, I checked this file and (of course) all these
warnings are old ones, caused by a missing __iomem in the assignments:
	struct fsl_spi_reg *reg_base = mspi->reg_base;

Why some are shown as new and some as old is a mystery to me.

-- Luc