[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240730-sitzplatz-vollbad-c269e4298a58@brauner>
Date: Tue, 30 Jul 2024 14:12:33 +0200
From: Christian Brauner <brauner@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the vfs-brauner tree
On Tue, Jul 30, 2024 at 09:00:59AM GMT, Stephen Rothwell wrote:
> Hi all,
>
> On Fri, 26 Jul 2024 10:00:41 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > After merging the vfs-brauner tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from fs/smb/server/unicode.c:14:
> > fs/smb/server/smb_common.h:46: error: "F_CREATED" redefined [-Werror]
> > 46 | #define F_CREATED 2
> > |
> > In file included from include/linux/fcntl.h:6,
> > from include/linux/fs.h:26,
> > from fs/smb/server/unicode.c:9:
> > include/uapi/linux/fcntl.h:20: note: this is the location of the previous definition
> > 20 | #define F_CREATED (F_LINUX_SPECIFIC_BASE + 4)
> > |
> > cc1: all warnings being treated as errors
> >
> > Caused by commit
> >
> > a621ce4eed14 ("fcntl: add F_CREATED")
> >
> > Is that commit really intended for this merge window?
> >
> > I have used the vfs-brauner tree from next-20240725 for today.
>
> I am still getting this build failure.
Sorry, this is now fixed!
Powered by blists - more mailing lists