[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b764819a-a7d6-6976-bc46-eab972566309@infradead.org>
Date: Wed, 31 Jan 2018 18:51:35 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: akpm@...ux-foundation.org, mm-commits@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-next@...r.kernel.org, sfr@...b.auug.org.au, mhocko@...e.cz,
broonie@...nel.org, linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: mmotm 2018-01-31-16-51 uploaded (f2fs)
On 01/31/2018 04:52 PM, akpm@...ux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-01-31-16-51 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (4.x
> or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
It looks like this build error is not from an mmotm patch but from mainline
or linux-next:
on i386:
../fs/f2fs/super.c: In function 'f2fs_fill_super':
../fs/f2fs/super.c:2563:18: error: 'SB_I_CGROUPWB' undeclared (first use in this function)
sb->s_iflags |= SB_I_CGROUPWB;
^
Anyway, it's an unknown value.
--
~Randy
Powered by blists - more mailing lists