From: Glenn Washburn <email@example.com>
To: Christian Brauner <firstname.lastname@example.org>
Cc: linux-um <email@example.com>,
Richard Weinberger <firstname.lastname@example.org>,
Johannes Berg <email@example.com>,
Anton Ivanov <firstname.lastname@example.org>,
Seth Forshee <email@example.com>
Subject: Re: Which branch should this patch be based against?
Date: Tue, 28 Feb 2023 18:42:16 -0600 [thread overview]
Message-ID: <20230228184216.09e96361@crass-HP-ZBook-15-G2> (raw)
On Tue, 28 Feb 2023 10:01:42 +0100
Christian Brauner <firstname.lastname@example.org> wrote:
> On Mon, Feb 27, 2023 at 10:33:36AM -0600, Glenn Washburn wrote:
> > Hi,
> > On Fri, 27 Jan 2023 19:41:59 -0600
> > Glenn Washburn <email@example.com> wrote:
> > > Let hostfs handle idmapped mounts. This allows to have the same
> > > hostfs mount appear in multiple locations with different id
> > > mappings.
> > This patch is based off of linux-next in the Richard's UML repo.
> > However, I've noticed that this patch needs some modifications to be
> > applied against the tip. So I'm wondering which branch in what
> > repo is best to base patches from?
> Hey Glenn,
> Linus merged my pull request that introduces a dedicated new type for
> idmapped mounts into the vfs: struct mnt_idmap. So any branch you base
> this on should contain that work. Let me know if you need help with
> the conversion.
I was about to ask for help yesterday when I was trying to figure it
out, but I think I got it working. However, you probably will have
suggestions for improvement. I'll send an updated version soon, and
make sure you're explicitly included.
linux-um mailing list
prev parent reply other threads:[~2023-03-01 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 1:41 [PATCH] hostfs: handle idmapped mounts Glenn Washburn
2023-02-27 16:33 ` Which branch should this patch be based against? Glenn Washburn
2023-02-28 9:01 ` Christian Brauner
2023-03-01 0:42 ` Glenn Washburn [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).