From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>,
kbuild-all@01.org, "Johannes Weiner" <hannes@cmpxchg.org>,
"Linux Memory Management List" <linux-mm@kvack.org>
Subject: Re: [mmotm:master 119/211] mm/migrate.c:2184:5: note: in expansion of macro 'MIGRATE_PFN_DEVICE'
Date: Thu, 16 Mar 2017 20:41:35 -0700 [thread overview]
Message-ID: <20170316204135.da11fb9a50d22c264404a30e@linux-foundation.org> (raw)
In-Reply-To: <201703170923.JOG5lvVO%fengguang.wu@intel.com>
On Fri, 17 Mar 2017 09:46:30 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: git://git.cmpxchg.org/linux-mmotm.git master
> head: 8276ddb3c638602509386f1a05f75326dbf5ce09
> commit: a6d9a210db7db40e98f7502608c6f1413c44b9b9 [119/211] mm/hmm/migrate: support un-addressable ZONE_DEVICE page in migration
heh, I think the HMM patchset just scored the world record number of
build errors. Thanks for doing this.
But why didn't we find out earlier than v18? Don't you scoop patchsets
off the mailing list *before* someone merges them into an upstream
tree?
--
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>
next prev parent reply other threads:[~2017-03-17 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 1:46 kbuild test robot
2017-03-17 3:41 ` Andrew Morton [this message]
2017-03-17 4:06 ` [kbuild-all] " Fengguang Wu
2017-03-17 22:48 ` Jerome Glisse
2017-03-18 12:48 ` Philip Li
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=20170316204135.da11fb9a50d22c264404a30e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
/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