linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Yang Xu <xuyang2018.jy@fujitsu.com>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	Seth Forshee <sforshee@kernel.org>
Subject: Re: [PATCH v2] overlayfs: improve ovl_get_acl
Date: Wed, 3 Aug 2022 09:43:56 +0200	[thread overview]
Message-ID: <20220803074356.bpo2tbfdfc6iifan@wittgenstein> (raw)
In-Reply-To: <CAJfpegst_95cCUd_LWg0i1X=KfD3wy3ExXnekkj+=6Ku7bB76A@mail.gmail.com>

On Tue, Aug 02, 2022 at 03:46:00PM +0200, Miklos Szeredi wrote:
> On Thu, 28 Jul 2022 at 16:23, Christian Brauner <brauner@kernel.org> wrote:
> >
> > On Thu, Jul 28, 2022 at 03:06:21PM +0200, Miklos Szeredi wrote:
> > > On Thu, 28 Jul 2022 at 03:48, Yang Xu <xuyang2018.jy@fujitsu.com> wrote:
> > > >
> > > > Provide a proper stub for the !CONFIG_FS_POSIX_ACL case.
> > >
> > > Applied, thanks.
> >
> > Hey Miklos,
> >
> > Just an fyi that this will likely introduce a (somewhat minor) merge
> > conflict with the series to fix POSIX ACLs with overlayfs on top of
> > idmapped layers that I mentioned to you a few weeks ago in [1].
> >
> > The series is - as announced in the mail above - in [2] and been in next
> > for quite a while now.
> >
> > It's right before the mw so ideally I wouldn't want to rebase. Let me
> > know if I you want me to do anything. Ideally you could probably just
> > wait until I sent the PR next week.
> 
> Okay, thanks for the heads up.

Fyi, this has now been merged into mainline!

Thanks!
Christian

      reply	other threads:[~2022-08-03  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  2:49 [PATCH v2] overlayfs: improve ovl_get_acl Yang Xu
2022-07-28 13:06 ` Miklos Szeredi
2022-07-28 14:23   ` Christian Brauner
2022-08-02 13:46     ` Miklos Szeredi
2022-08-03  7:43       ` 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=20220803074356.bpo2tbfdfc6iifan@wittgenstein \
    --to=brauner@kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=sforshee@kernel.org \
    --cc=xuyang2018.jy@fujitsu.com \
    /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).