From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>,
Oleksij Rempel <o.rempel@pengutronix.de>,
adrian.hunter@intel.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Subject: Re: [PATCH v2 3/3] fs: ubifs: set s_uuid in super block
Date: Tue, 02 May 2017 10:23:18 +0300 [thread overview]
Message-ID: <1493709798.797.18.camel@gmail.com> (raw)
In-Reply-To: <5d7d0f21-d87f-0835-c2f6-b6c9e07f73a8@nod.at>
On Tue, 2017-04-11 at 22:43 +0200, Richard Weinberger wrote:
> Makes sense.
>
> Artem, do you remember why UBIFS didn't set s_uuid in first place?
Just did not notice it I think.
prev parent reply other threads:[~2017-05-02 7:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 9:50 [PATCH v2 0/3] make ubifs compatible with IMA and EVM Oleksij Rempel
2017-04-11 9:50 ` [PATCH v2 1/3] fs: ubifs: parse iversion mount option Oleksij Rempel
2017-04-11 9:50 ` [PATCH v2 2/3] fs: ubifs: update i_version on inode changes Oleksij Rempel
2017-04-11 16:05 ` Christoph Hellwig
2017-04-11 21:13 ` Richard Weinberger
2017-04-12 6:05 ` Oleksij Rempel
2017-04-12 6:08 ` Christoph Hellwig
2017-04-12 7:04 ` Oleksij Rempel
2017-04-24 15:44 ` Richard Weinberger
2017-04-11 9:50 ` [PATCH v2 3/3] fs: ubifs: set s_uuid in super block Oleksij Rempel
2017-04-11 20:43 ` Richard Weinberger
2017-04-12 5:48 ` Christoph Hellwig
2017-04-12 7:15 ` Oleksij Rempel
2017-04-24 15:47 ` Richard Weinberger
2017-04-27 22:03 ` Richard Weinberger
2017-04-28 8:53 ` Amir Goldstein
2017-05-02 5:30 ` Oleksij Rempel
2017-05-02 7:19 ` Amir Goldstein
2017-05-02 7:37 ` Richard Weinberger
2017-05-09 4:13 ` Oleksij Rempel
[not found] ` <CAOQ4uxiEGJLSGS5rK8V8GRNvf9aWqbVG5odu2=nv73xTOmvfNQ@mail.gmail.com>
2017-05-09 5:52 ` Oleksij Rempel
2017-05-09 7:01 ` Richard Weinberger
2017-05-09 7:08 ` Amir Goldstein
2017-05-09 7:35 ` Oleksij Rempel
2017-05-09 7:35 ` Richard Weinberger
2017-05-09 7:50 ` Amir Goldstein
2017-05-02 7:23 ` Artem Bityutskiy [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=1493709798.797.18.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=o.rempel@pengutronix.de \
--cc=richard@nod.at \
--cc=s.trumtrar@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.