From: Matthew Wilcox <willy@infradead.org>
To: Philip Li <philip.li@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>, kbuild test robot <lkp@intel.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
x86@kernel.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, kbuild-all@01.org
Subject: Re: [kbuild-all] [vfs:hch.aio 7/40] include/linux/syscalls.h:233:18: warning: 'sys_io_pgetevents' alias between functions of incompatible types 'long int(aio_context_t, long int, long int, struct io_event *, struct timespec *, const struct __aio_sigset *)' and 'long int(long int, long int, long int, long int, long int, long int)'
Date: Tue, 29 May 2018 04:29:31 -0700 [thread overview]
Message-ID: <20180529112931.GA24842@bombadil.infradead.org> (raw)
In-Reply-To: <20180529080507.GA4990@intel.com>
On Tue, May 29, 2018 at 04:05:07PM +0800, Philip Li wrote:
> On Tue, May 29, 2018 at 09:20:24AM +0200, Greg Kroah-Hartman wrote:
> > I was seeing this type of mess when trying to build with gcc-8.1, and
> > could not figure it out either. So I just gave up and went back to
> > gcc-7 for the time being. I don't think it's anything new you did here.
> thanks, we will follow up to exclude this pattern in report in bot side.
I don't think that's the right solution here. People just don't want
to see errors/warnings that they didn't introduce. It'd be unfortunate
to start skipping warnings about syscalls entirely.
next prev parent reply other threads:[~2018-05-29 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 3:12 [vfs:hch.aio 7/40] include/linux/syscalls.h:233:18: warning: 'sys_io_pgetevents' alias between functions of incompatible types 'long int(aio_context_t, long int, long int, struct io_event *, struct timespec *, const struct __aio_sigset *)' and 'long int(long int, long int, long int, long int, long int, long int)' kbuild test robot
2018-05-29 7:20 ` Christoph Hellwig
2018-05-29 7:20 ` Greg Kroah-Hartman
2018-05-29 8:05 ` [kbuild-all] " Philip Li
2018-05-29 11:29 ` Matthew Wilcox [this message]
2018-05-29 13:00 ` Greg Kroah-Hartman
2018-05-29 14:59 ` Philip Li
2018-05-29 14:58 ` Philip Li
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=20180529112931.GA24842@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=philip.li@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).