From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux FS Devel <linux-fsdevel@vger•kernel.org>,
Jan Kara <jack@suse•cz>, Amir Goldstein <amir73il@gmail•com>
Subject: Re: linux-next: Tree for Feb 14 (fanotify)
Date: Thu, 14 Feb 2019 07:58:33 -0800 [thread overview]
Message-ID: <b005f0f9-6db1-e9dc-a04c-bf37b37be8ce@infradead.org> (raw)
In-Reply-To: <20190214175138.3f69ec91@canb.auug.org.au>
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
next prev parent reply other threads:[~2019-02-14 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 6:51 linux-next: Tree for Feb 14 Stephen Rothwell
2019-02-14 15:58 ` Randy Dunlap [this message]
2019-02-14 16:49 ` linux-next: Tree for Feb 14 (fanotify) Jan Kara
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=b005f0f9-6db1-e9dc-a04c-bf37b37be8ce@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=amir73il@gmail$(echo .)com \
--cc=jack@suse$(echo .)cz \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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