From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============3886984818091501026==" MIME-Version: 1.0 From: Christoph Hellwig To: kbuild-all@lists.01.org Subject: Re: [hch-misc:sockopt-cleanups 17/22] net/ipv4/ip_sockglue.c:1489:13: sparse: sparse: incorrect type in initializer (different address spaces) Date: Sat, 18 Jul 2020 09:02:09 +0200 Message-ID: <20200718070209.GA6185@lst.de> In-Reply-To: <20200717212449.GG437393@lianli.shorne-pla.net> List-Id: --===============3886984818091501026== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Sat, Jul 18, 2020 at 06:24:49AM +0900, Stafford Horne wrote: > On Fri, Jul 17, 2020 at 06:40:11PM +0200, Christoph Hellwig wrote: > > As far as I can tell the sparse annotations in the openrisc headers > > are all messed up, and this is caused by that (just as the other one). > > = > > Can you guys drop openriscv sparse runs for now? > > = > > Or can the openrisc maintainers tries to fix up the sparse annotations > > in their uaccess macros? > > = > I will have a look at it. I have this patch on my queue that fixes one i= ssue, > not sure if its fixes "all" issues, I never used sparse until now. > = > I was planning to send this during the 5.9 merge window, but I can send n= ow if > its urgent. I don't think it is urgent. I just try to follow up to buildbot reports instead of letting them slip. --===============3886984818091501026==--