From: Al Viro <viro@ZenIV.linux.org.uk>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: Re: [vfs:work.aio 4/4] fs/aio.c:1893:36: error: 'iocbpp' undeclared; did you mean 'iocb'?
Date: Mon, 28 May 2018 00:12:01 +0100 [thread overview]
Message-ID: <20180527231201.GU30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <201805280756.Lizjo1TG%fengguang.wu@intel.com>
On Mon, May 28, 2018 at 07:04:58AM +0800, kbuild test robot wrote:
> All error/warnings (new ones prefixed by >>):
>
> In file included from include/linux/kernel.h:10:0,
> from fs/aio.c:14:
> fs/aio.c: In function '__do_compat_sys_io_submit':
> >> fs/aio.c:1893:36: error: 'iocbpp' undeclared (first use in this function); did you mean 'iocb'?
*blink*
iocb it is, indeed, but... I wonder how the hell has it not been caught
on local tests
prev parent reply other threads:[~2018-05-27 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 23:04 [vfs:work.aio 4/4] fs/aio.c:1893:36: error: 'iocbpp' undeclared; did you mean 'iocb'? kbuild test robot
2018-05-27 23:12 ` Al Viro [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=20180527231201.GU30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
/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).