[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <12fa4586-a47d-4b6f-7b3c-23a036e45f8d@infradead.org>
Date: Fri, 15 May 2020 08:06:00 -0700
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>,
Al Viro <viro@...IV.linux.org.uk>,
David Howells <dhowells@...hat.com>
Subject: Re: linux-next: Tree for May 12 (fs/namespace.c)
On 5/12/20 8:12 AM, Randy Dunlap wrote:
> On 5/12/20 5:54 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: there will be no linux-next release tomorrow.
>>
>> Changes since 20200511:
>>
>> New trees: notifications, fsinfo
>>
>
> on i386 or x86_64:
>
> CC fs/namespace.o
> ../fs/namespace.c: In function ‘fsinfo_generic_mount_topology’:
> ../fs/namespace.c:4274:42: error: ‘struct mount’ has no member named ‘mnt_topology_changes’
> p->mnt_topology_changes = atomic_read(&m->mnt_topology_changes);
> ^~
>
> i.e., CONFIG_MOUNT_NOTIFICATIONS is not set/enabled.
>
> Full randconfig file is attached.
>
This build error is still present in linux-next 20200515.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@...radead.org>
Powered by blists - more mailing lists