From: Christian Brauner <brauner@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [GIT PULL] overlayfs backing file helpers for 6.8
Date: Sat, 23 Dec 2023 20:51:16 +0100 [thread overview]
Message-ID: <20231223-jagdsaison-querschnitt-b52158ca1d48@brauner> (raw)
In-Reply-To: <20231223154405.941062-1-amir73il@gmail.com>
On Sat, 23 Dec 2023 17:44:05 +0200, Amir Goldstein wrote:
> Please pull the overlayfs backing file helpers for 6.8.
>
> The only change since the patches that you reviewed [1] is that I added
> assertion to all the helpers that file is a backing_file as you requested.
>
> This branch merges cleanly with master branch of the moment.
>
> This branch depends on and is based on top of vfs.rw branch in your tree.
> When test merging with vfs.all of the moment, there is a trivial conflict
> in MAINTAINERS file with the vfs.netfs branch.
>
> [...]
Pulled into the vfs.rw branch of the vfs/vfs.git tree.
Patches in the vfs.rw branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series or pull request allowing us to
drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.rw
https://git.kernel.org/vfs/vfs/c/7a18c0fff41e
prev parent reply other threads:[~2023-12-23 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 15:44 [GIT PULL] overlayfs backing file helpers for 6.8 Amir Goldstein
2023-12-23 19:51 ` Christian Brauner [this message]
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=20231223-jagdsaison-querschnitt-b52158ca1d48@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.