From: Miklos Szeredi <miklos@szeredi.hu>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Vivek Goyal <vgoyal@redhat.com>,
overlayfs <linux-unionfs@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] ovl introduce "uuid=off"
Date: Fri, 30 Oct 2020 14:57:13 +0100 [thread overview]
Message-ID: <CAJfpegvvaN0O1PGnq6rLSA-XnseuPcaSGZDeA7uG6WA7ftCfYQ@mail.gmail.com> (raw)
In-Reply-To: <20201013145954.4274-1-ptikhomirov@virtuozzo.com>
On Tue, Oct 13, 2020 at 5:00 PM Pavel Tikhomirov
<ptikhomirov@virtuozzo.com> wrote:
>
> This is a v5 of:
> ovl: introduce new "index=nouuid" option for inodes index feature
>
> Changes in v3: rebase to overlayfs-next, replace uuid with null in file
> handles, propagate ovl_fs to needed functions in a separate patch, add
> separate bool "uuid=on/off" option, fix numfs check fallback, add a note
> to docs.
>
> Changes in v4: get rid of double negatives, remove nouuid leftower
> comment, fix missprint in kernel config name.
>
> Changes in v5: fix typos; remove config option and module param.
>
> Amir, as second patch had changed quiet a bit, I don't add you
> reviewed-by to it.
>
> CC: Amir Goldstein <amir73il@gmail.com>
> CC: Vivek Goyal <vgoyal@redhat.com>
> CC: Miklos Szeredi <miklos@szeredi.hu>
> CC: linux-unionfs@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
> Signed-off-by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Thanks, applied.
Miklos
prev parent reply other threads:[~2020-10-30 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 14:59 [PATCH v5 0/2] ovl introduce "uuid=off" Pavel Tikhomirov
2020-10-13 14:59 ` [PATCH v5 1/2] ovl: propagate ovl_fs to ovl_decode_real_fh and ovl_encode_real_fh Pavel Tikhomirov
2020-10-13 14:59 ` [PATCH v5 2/2] ovl: introduce new "uuid=off" option for inodes index feature Pavel Tikhomirov
2020-10-13 16:23 ` Amir Goldstein
2020-10-30 13:57 ` Miklos Szeredi [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=CAJfpegvvaN0O1PGnq6rLSA-XnseuPcaSGZDeA7uG6WA7ftCfYQ@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=amir73il@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=vgoyal@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).