From: Christian Brauner <brauner@kernel.org>
To: Glenn Washburn <development@efficientek.com>
Cc: linux-um <linux-um@lists.infradead.org>,
Richard Weinberger <richard@nod.at>,
Johannes Berg <johannes@sipsolutions.net>,
Anton Ivanov <anton.ivanov@kot-begemot.co.uk>,
Seth Forshee <sforshee@kernel.org>
Subject: Re: Which branch should this patch be based against?
Date: Tue, 28 Feb 2023 10:01:42 +0100 [thread overview]
Message-ID: <20230228090142.y4dcxxzdkycbyobj@wittgenstein> (raw)
In-Reply-To: <20230227103336.6bd56246@crass-HP-ZBook-15-G2>
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 <development@efficientek.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[1].
> However, I've noticed that this patch needs some modifications to be
> applied against the tip[2]. 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.
Christian
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-02-28 9:01 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 [this message]
2023-03-01 0:42 ` Glenn Washburn
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=20230228090142.y4dcxxzdkycbyobj@wittgenstein \
--to=brauner@kernel.org \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=development@efficientek.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=sforshee@kernel.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 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).