From: Christoph Hellwig <hch@lst.de>
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 [thread overview]
Message-ID: <20200718070209.GA6185@lst.de> (raw)
In-Reply-To: <20200717212449.GG437393@lianli.shorne-pla.net>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
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 issue,
> 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 now if
> its urgent.
I don't think it is urgent. I just try to follow up to buildbot reports
instead of letting them slip.
prev parent reply other threads:[~2020-07-18 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 14:07 [hch-misc:sockopt-cleanups 17/22] net/ipv4/ip_sockglue.c:1489:13: sparse: sparse: incorrect type in initializer (different address spaces) kernel test robot
2020-07-17 16:40 ` Christoph Hellwig
2020-07-17 21:24 ` Stafford Horne
2020-07-18 7:02 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200718070209.GA6185@lst.de \
--to=hch@lst.de \
--cc=kbuild-all@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.