[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOQ4uxjazEO_f7HPzUpK3FpZXC4j=GXFfBpgNU9zsanVzp=Kzg@mail.gmail.com>
Date: Fri, 13 Oct 2023 09:32:41 +0300
From: Amir Goldstein <amir73il@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Christian Brauner <brauner@...nel.org>,
Miklos Szeredi <miklos@...redi.hu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the vfs-brauner tree
On Fri, Oct 13, 2023 at 2:48 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> The following commits are also in the overlayfs tree as different commits
> (but the same patches):
>
> 149f455798a6 ("smb: move cifs_xattr_handlers to .rodata")
> 295d3c441226 ("net: move sockfs_xattr_handlers to .rodata")
> 2f5028604f08 ("shmem: move shmem_xattr_handlers to .rodata")
> 375aa21d36ee ("xfs: move xfs_xattr_handlers to .rodata")
> 3d649a4a832e ("overlayfs: move xattr tables to .rodata")
> c08a831c74f0 ("squashfs: move squashfs_xattr_handlers to .rodata")
> c25308c326db ("ubifs: move ubifs_xattr_handlers to .rodata")
>
> Looks like the overlatfs tree has merged a previous verion of a topic
> branch from the vfs-brauner tree.
Yeh, sorry my bad.
Christian told me that vfs.xattr branch was stable, but I did not notice
that I had merged a day old version.
Fixed now.
BTW, Christian, feel free to fast forward the stable vfs.xattr branch to
a640d888953c const_structs.checkpatch: add xattr_handler
it won't be a problem for me.
Thanks,
Amir.
Powered by blists - more mailing lists