[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b005f0f9-6db1-e9dc-a04c-bf37b37be8ce@infradead.org>
Date: Thu, 14 Feb 2019 07:58:33 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Jan Kara <jack@...e.cz>, Amir Goldstein <amir73il@...il.com>
Subject: Re: linux-next: Tree for Feb 14 (fanotify)
On 2/13/19 10:51 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190213:
>
seen on i386:
when # CONFIG_EXPORTFS_BLOCK_OPS is not set:
ld: fs/notify/fanotify/fanotify.o: in function `fanotify_alloc_event':
fanotify.c:(.text+0x25a): undefined reference to `exportfs_encode_inode_fh'
ld: fanotify.c:(.text+0x29e): undefined reference to `exportfs_encode_inode_fh'
--
~Randy
Powered by blists - more mailing lists