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;
MIME-Version: 1.0
References: <20200617220226.88948-1-luc.vanoostenryck@gmail.com> <202006181747.1x7hGaZR%lkp@intel.com>
In-Reply-To: <202006181747.1x7hGaZR%lkp@intel.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu, 18 Jun 2020 09:59:05 -0700
Message-ID: <CAHk-=wi=y6XoZKjxoGf9h4Zj3SPZnA+g5ZjsZ2hKT-AZW7H0ag@mail.gmail.com>
Subject: Re: [PATCH] sparse: use identifiers to define address spaces
To:     kernel test robot <lkp@intel.com>
Cc:     Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
        kbuild-all@lists.01.org, LKML <linux-kernel@vger.kernel.org>,
        Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Jun 18, 2020 at 3:06 AM kernel test robot <lkp@intel.com> wrote:
>
> I love your patch! Perhaps something to improve:

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.

I'm planning on applying that patch soon, so this is just a heads-up
that that will (again) cause the big number of warning string changes,
but hopefully that will be a one-time event and the test robot will
learn.

             Linus