linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-next@vger.kernel.org, sfr@canb.auug.org.au, mhocko@suse.cz,
	broonie@kernel.org, jack@suse.cz
Subject: Re: mmotm 2016-05-19-19-59 uploaded
Date: Fri, 20 May 2016 14:36:28 +0900	[thread overview]
Message-ID: <20160520053628.GB6808@bbox> (raw)
In-Reply-To: <20160520051417.GA6808@bbox>

Ccing Jan,

dax: Remove complete_unwritten argument

On Fri, May 20, 2016 at 02:14:17PM +0900, Minchan Kim wrote:
> On Thu, May 19, 2016 at 07:59:50PM -0700, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2016-05-19-19-59 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.
> > 
> > This tree is partially included in linux-next.  To see which patches are
> > included in linux-next, consult the `series' file.  Only the patches
> > within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> > linux-next.
> > 
> > A git tree which contains the memory management portion of this tree is
> > maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> > by Michal Hocko.  It contains the patches which are between the
> > "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
> > file, http://www.ozlabs.org/~akpm/mmotm/series.
> > 
> > 
> > A full copy of the full kernel tree with the linux-next and mmotm patches
> > already applied is available through git within an hour of the mmotm
> > release.  Individual mmotm releases are tagged.  The master branch always
> > points to the latest release, so it's constantly rebasing.
> > 
> > http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
> > 
> > To develop on top of mmotm git:
> > 
> >   $ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> >   $ git remote update mmotm
> >   $ git checkout -b topic mmotm/master
> >   <make changes, commit>
> >   $ git send-email mmotm/master.. [...]
> > 
> > To rebase a branch with older patches to a new mmotm release:
> > 
> >   $ git remote update mmotm
> >   $ git rebase --onto mmotm/master <topic base> topic
> > 
> > 
> > 
> > 
> > The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> > contains daily snapshots of the -mm tree.  It is updated more frequently
> > than mmotm, and is untested.
> > 
> > A git copy of this tree is available at
> > 
> > 	http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/
> > 
> > and use of this tree is similar to
> > http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above.
> > 
> 
> In first build, I got this.
> 
> In file included from mm/filemap.c:14:0:
> include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
>    dax_iodone_t);
>    ^
> include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
>    dax_iodone_t);
>    ^
> include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
>      dax_iodone_t di)
>      ^
> In file included from mm/vmscan.c:49:0:
> include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
>    dax_iodone_t);
>    ^
> include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
>    dax_iodone_t);
>    ^
> include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
>      dax_iodone_t di)
>      ^
> In file included from mm/truncate.c:12:0:
> include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
>    dax_iodone_t);
>    ^
> include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
>    dax_iodone_t);
>    ^
> include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
>      dax_iodone_t di)
>      ^
> make[1]: *** [mm/truncate.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make[1]: *** [mm/filemap.o] Error 1
> make[1]: *** [mm/vmscan.o] Error 1
> make: *** [mm/] Error 2
> 
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-05-20  5:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20  2:59 mmotm 2016-05-19-19-59 uploaded akpm
2016-05-20  3:27 ` Stephen Rothwell
2016-05-20  5:14 ` Minchan Kim
2016-05-20  5:36   ` Minchan Kim [this message]
2016-05-20  5:39     ` Andrew Morton
2016-05-20 10:31       ` Jan Kara

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=20160520053628.GB6808@bbox \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).