From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <brauner@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL for v6.7] vfs super updates
Date: Mon, 30 Oct 2023 09:20:09 +1100 [thread overview]
Message-ID: <20231030092009.0880e5f3@canb.auug.org.au> (raw)
In-Reply-To: <20231027-vfs-super-aa4b9ecfd803@brauner>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
Hi Christian,
On Sat, 28 Oct 2023 16:02:33 +0200 Christian Brauner <brauner@kernel.org> wrote:
>
> The vfs.super tree originally contained a good chunk of the btrfs tree
> as a merge - as mentioned elsewhere - since we had intended to depend on
> work that Christoph did a few months ago. We had allowed btrfs to carry
> the patches themselves.
>
> But it since became clear that btrfs/for-next likely does not contain
> any of the patches there's zero reason for the original merge. So the
> merge is dropped. It's not great because it's a late change but it's
> better than bringing in a completely pointless merge.
Can you please update what you are including in linux-next to match
what you are asking Linus to merge.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-10-29 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 14:02 [GIT PULL for v6.7] vfs super updates Christian Brauner
2023-10-29 22:20 ` Stephen Rothwell [this message]
2023-10-30 8:29 ` Christian Brauner
2023-10-30 20:05 ` pr-tracker-bot
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=20231030092009.0880e5f3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.