linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Glenn Washburn <development@efficientek.com>
To: 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>
Subject: Which branch should this patch be based against?
Date: Mon, 27 Feb 2023 10:33:36 -0600	[thread overview]
Message-ID: <20230227103336.6bd56246@crass-HP-ZBook-15-G2> (raw)
In-Reply-To: <20230128014159.1741728-1-development@efficientek.com>

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?

Glenn

[1] git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git
[2] git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

  reply	other threads:[~2023-02-27 16:33 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 ` Glenn Washburn [this message]
2023-02-28  9:01   ` Which branch should this patch be based against? Christian Brauner
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=20230227103336.6bd56246@crass-HP-ZBook-15-G2 \
    --to=development@efficientek.com \
    --cc=anton.ivanov@kot-begemot.co.uk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    /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).