[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240125-mochten-lauftraining-9fa7ac4a3461@brauner>
Date: Thu, 25 Jan 2024 17:21:22 +0100
From: Christian Brauner <brauner@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Baokun Li <libaokun1@...wei.com>,
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 Wed, Jan 24, 2024 at 10:35:37PM +1100, Stephen Rothwell wrote:
> Hi Christian,
>
> On Wed, 24 Jan 2024 12:13:02 +0100 Christian Brauner <brauner@...nel.org> wrote:
> >
> > I had dropped both from vfs.misc yesterday night. Maybe it didn't make
> > it in time.
>
> It still has not ... I only fetch your vfs.all branch. Did you remerge
> and push it out?
So vfs.all should be at:
commit 8577a331532bb1d75f3536461739a0a8e15b219c
Merge: 0c5c260545bd 06b8db3a7dde
Author: Christian Brauner <brauner@...nel.org>
AuthorDate: Wed Jan 24 18:33:30 2024 +0100
Commit: Christian Brauner <brauner@...nel.org>
CommitDate: Wed Jan 24 18:33:30 2024 +0100
Merge branch 'vfs.fs' into vfs.all
Signed-off-by: Christian Brauner <brauner@...nel.org>
And that should've contain a merge of vfs.misc with all problematic
patches dropped. Please yell if you still see an issue tomorrow!
Powered by blists - more mailing lists