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>,
Al Viro <viro@ZenIV.linux.org.uk>,
David Howells <dhowells@redhat.com>
Subject: Re: linux-next: Tree for May 12 (fs/namespace.c)
Date: Fri, 15 May 2020 08:06:00 -0700 [thread overview]
Message-ID: <12fa4586-a47d-4b6f-7b3c-23a036e45f8d@infradead.org> (raw)
In-Reply-To: <22d91c05-49ed-0c32-ba02-e2ded4947f46@infradead.org>
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@infradead.org>
next prev parent reply other threads:[~2020-05-15 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 12:54 linux-next: Tree for May 12 Stephen Rothwell
2020-05-12 15:12 ` linux-next: Tree for May 12 (fs/namespace.c) Randy Dunlap
2020-05-15 15:06 ` Randy Dunlap [this message]
2020-05-19 16:51 ` David Howells
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=12fa4586-a47d-4b6f-7b3c-23a036e45f8d@infradead.org \
--to=rdunlap@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
/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).