Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 4 Oct 2018 00:29:52 +0200
From:   Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To:     Larry Finger <Larry.Finger@lwfinger.net>
Cc:     LKML <linux-kernel@vger.kernel.org>,
        Christopher Li <sparse@chrisli.org>,
        Randy Dunlap <rdunlap@infradead.org>
Subject: Re: Sparse warnings from calls to max3() and max
Message-ID: <20181003222951.5vp47nf5x7ipyyi2@ltop.local>
References: <3afaa0ad-33a1-33d1-f306-8e0e467936dd@lwfinger.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3afaa0ad-33a1-33d1-f306-8e0e467936dd@lwfinger.net>
User-Agent: NeoMutt/20180622
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Oct 02, 2018 at 06:44:39PM -0500, Larry Finger wrote:
> Hi,
> 
> Sparse has suddenly started issuing as many as 11 warnings of
> "expression using sizeof(void)" for each call to max3(). There are
> similar warnings for calls to max(), thus I think this is the origin
> of the problem. My sparse version is 20180324-1.3-x86_64 installed
> in openSUSE Tumbleweed. My kernel is 4.19.0-rc6.

Hi,

This problem is resolved in a more recent version of sparse,
the one you can find at:
  git://github.com/lucvoo/sparse-dev

See Linus' email about it:
  https://lore.kernel.org/lkml/CA+55aFzYEnZR2GZLR-DwpONjMNYGYoDy+6AWLCVNayWiaZuqoA@mail.gmail.com/T/#u

NB. The official version hosted on kernel.org is not uptodate but
    I hope this will solved in a few weeks.

Best regards,
-- Luc Van Oostenryck