linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Alexander Larsson <alexl@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
	Miklos Szeredi <mszeredi@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: Re: [PATCH] ovl: move all parameter handling into params.{c,h}
Date: Tue, 4 Jul 2023 18:13:53 +0300	[thread overview]
Message-ID: <CAOQ4uxhkMYMnPL81RoWdnxCsiNtf-AbBVPcRj=hbo4vd8yp=QA@mail.gmail.com> (raw)
In-Reply-To: <CAL7ro1GgW-2gUhB=TBxwDAiybbQBbFabkU2tBNbBH85Q_KZWew@mail.gmail.com>

On Mon, Jul 3, 2023 at 12:16 PM Alexander Larsson <alexl@redhat.com> wrote:
>
> On Mon, Jun 26, 2023 at 4:40 PM Amir Goldstein <amir73il@gmail.com> wrote:
> >
> > On Mon, Jun 26, 2023 at 1:23 PM Christian Brauner <brauner@kernel.org> wrote:
> > >
> > > While initially I thought that we couldn't move all new mount api
> > > handling into params.{c,h} it turns out it is possible. So this just
> > > moves a good chunk of code out of super.c and into params.{c,h}.
> > >
> > > Signed-off-by: Christian Brauner <brauner@kernel.org>
> > > ---
> > >
> >
> > Thank you for this cleanup!
> >
> > Alex,
> >
> > I took the liberty to resolve the conflicts with your branch, see:
> >
> > https://github.com/amir73il/linux/commits/overlay-verity
>
> Thanks, I took a look at this and it seems good. Updated my branch to this too.
>

FYI, I pushed this cleanup commit to overlayfs-next, so
you can rebase overlay-verity v5 on top of that.

I will send this cleanup to Linus, so we have a clean slate for
the 6.6 cycle.

Thanks,
Amir.

  reply	other threads:[~2023-07-04 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 10:23 [PATCH] ovl: move all parameter handling into params.{c,h} Christian Brauner
2023-06-26 14:40 ` Amir Goldstein
2023-07-03  9:16   ` Alexander Larsson
2023-07-04 15:13     ` Amir Goldstein [this message]
2023-07-05  9:13       ` Alexander Larsson

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='CAOQ4uxhkMYMnPL81RoWdnxCsiNtf-AbBVPcRj=hbo4vd8yp=QA@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=alexl@redhat.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=mszeredi@redhat.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).