From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from zeniv.linux.org.uk ([195.92.253.2]:51684 "EHLO
        ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751893AbeE0XMF (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Sun, 27 May 2018 19:12:05 -0400
Date: Mon, 28 May 2018 00:12:01 +0100
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'?
Message-ID: <20180527231201.GU30522@ZenIV.linux.org.uk>
References: <201805280756.Lizjo1TG%fengguang.wu@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201805280756.Lizjo1TG%fengguang.wu@intel.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

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