Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
MIME-Version: 1.0
References: <20231019101231.174f1124@canb.auug.org.au>
In-Reply-To: <20231019101231.174f1124@canb.auug.org.au>
From:   Amir Goldstein <amir73il@gmail.com>
Date:   Thu, 19 Oct 2023 08:36:40 +0300
Message-ID: <CAOQ4uxh8ydr+YdyKtD9yR1_kpkqkt+MdjvAzkA48F2UNSxz40w@mail.gmail.com>
Subject: Re: linux-next: duplicate patches in the vfs-brauner tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Christian Brauner <brauner@kernel.org>,
        Miklos Szeredi <miklos@szeredi.hu>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Thu, Oct 19, 2023 at 2:12=E2=80=AFAM Stephen Rothwell <sfr@canb.auug.org=
.au> wrote:
>
> Hi all,
>
> The following commits are also in the overlayfs tree as different
> commits (but the same patches):
>
>   b8a42d441199 ("fs: export mnt_{get,put}_write_access() to modules")
>   5363f9742437 ("fs: rename __mnt_{want,drop}_write*() helpers")
>
> These are commits
>
>   ddf9e2ff67a9 ("fs: export mnt_{get,put}_write_access() to modules")
>   3e15dcf77b23 ("fs: rename __mnt_{want,drop}_write*() helpers")
>
> in the overlayfs tree.
>

Christian,

Did you apply those commits by mistake when you rebased vfs.misc
instead of merging vfs.mount.write into vfs.misc as it was prior to rebase?

Maybe it would be easier to rebase vfs.misc over vfs.mount.write?
with the intention of including these two patches inside a larger PR?

ATM, overlayfs-next relies on two vfs branches as being stable:
vfs.mount.write and vfs.xattr.

It's not a problem for me to rebase on any other stable branches
that include those changes if you wish to reorganize the vfs topic
branches differently.

Thanks,
Amir.