[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOQ4uxgn59hxAOgRD87VdVPv2srtcLjoFCVVrkAnezEN0_ZFxg@mail.gmail.com>
Date: Tue, 9 May 2017 10:08:24 +0300
From: Amir Goldstein <amir73il@...il.com>
To: Richard Weinberger <richard@....at>
Cc: Oleksij Rempel <ore@...gutronix.de>,
Christoph Hellwig <hch@...radead.org>,
Artem Bityutskiy <dedekind1@...il.com>,
Adrian Hunter <adrian.hunter@...el.com>,
linux-mtd@...ts.infradead.org,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Steffen Trumtrar <s.trumtrar@...gutronix.de>
Subject: Re: [PATCH v2 3/3] fs: ubifs: set s_uuid in super block
On Tue, May 9, 2017 at 10:01 AM, Richard Weinberger <richard@....at> wrote:
>
> Oleksij,
>
> Am 09.05.2017 um 07:52 schrieb Oleksij Rempel:
> >>
> >> If VFS maintainers are fine with that, I'll take it.
> >> From UBIFS' POV it does not matter much. :-)
> >>
> >>
> >> Ping to VFS maintainers?
> >>
> >>
> >> What ping? Al made it clear that a flag is not needed.
> >> BTW, xfs s_uuid patch was merged to master.
> >
> >
> > I'm talking about ubifs patch.
Me too.
>
> Then we can queue this patch for 4.13.
> Please resend and make sure it addresses everything what was also
> suggested for the xfs s_uuid patch.
>
Just to be clear, the xfs s_uuid patch is just a memcpy,
no different from Oleksij's patch.
Thanks,
Amir.
Powered by blists - more mailing lists