linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Linux Memory Management List" <linux-mm@kvack.org>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	kbuild-all@01.org, "Johannes Weiner" <hannes@cmpxchg.org>
Subject: Re: [kbuild-all] [mmotm:master 119/211] mm/migrate.c:2184:5: note: in expansion of macro 'MIGRATE_PFN_DEVICE'
Date: Fri, 17 Mar 2017 12:06:08 +0800	[thread overview]
Message-ID: <20170317040608.islf67cjbe25rjnx@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20170316204135.da11fb9a50d22c264404a30e@linux-foundation.org>

Hi Andrew,

On Thu, Mar 16, 2017 at 08:41:35PM -0700, Andrew Morton wrote:
>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?

Yes we test LKML patches, however not all patches can be successfully
applied, so cannot be tested at all.

There is a way to significantly increase the chance of finding the
right git-apply base, however this idea needs buy-in by the GIT community:

        https://lkml.org/lkml/2017/3/9/956

Currently we rely on heuristics and try-outs to select a git base.
For this patchset, log shows it cannot be applied to all of these
common bases

- linus/master
- recent RC kernels
- mmotm/master
- linux-next/master


[2017-01-13 13:45:44] Applying to linus/master..linux-review/J-r-me-Glisse/mm-memory-hotplug-convert-device-bool-to-int-to-allow-for-more-flags-v2/20170113-134544
[2017-01-13 13:45:45] Applying to linux/master..linux-review/J-r-me-Glisse/mm-memory-hotplug-convert-device-bool-to-int-to-allow-for-more-flags-v2/20170113-134545
[2017-01-13 13:45:52] Applying to mmotm/master..linux-review/J-r-me-Glisse/mm-memory-hotplug-convert-device-bool-to-int-to-allow-for-more-flags-v2/20170113-134552
[2017-01-13 13:46:03] Applying to v4.9-rc8..linux-review/J-r-me-Glisse/mm-memory-hotplug-convert-device-bool-to-int-to-allow-for-more-flags-v2/20170113-134603
[2017-01-13 13:46:10] Applying to v4.9-rc7..linux-review/J-r-me-Glisse/mm-memory-hotplug-convert-device-bool-to-int-to-allow-for-more-flags-v2/20170113-134610
[2017-01-13 13:46:14] Applying to v4.9-rc6..linux-review/J-r-me-Glisse/mm-memory-hotplug-convert-device-bool-to-int-to-allow-for-more-flags-v2/20170113-134614
[2017-01-13 13:46:17] Applying to next-20170111..linux-review/J-r-me-Glisse/mm-memory-hotplug-convert-device-bool-to-int-to-allow-for-more-flags-v2/20170113-134617
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 01/15] mm/memory/hotplug: convert device bool to int to allow for more flags v2
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 02/15] mm/ZONE_DEVICE/devmem_pages_remove: allow early removal of device memory v2
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 03/15] mm/ZONE_DEVICE/free-page: callback when page is freed
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 04/15] mm/ZONE_DEVICE/unaddressable: add support for un-addressable device memory v2
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 05/15] mm/ZONE_DEVICE/x86: add support for un-addressable device memory
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 06/15] mm/hmm: heterogeneous memory management (HMM for short)
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 07/15] mm/hmm/mirror: mirror process address space on device with HMM helpers
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 08/15] mm/hmm/mirror: helper to snapshot CPU page table
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 09/15] mm/hmm/mirror: device page fault handler
[2017-01-13 13:46:25] >>> apply-failed: "JA(C)rA'me Glisse" <jglisse@redhat.com> [HMM v16 10/15] mm/hmm/migrate: support un-addressable ZONE_DEVICE page in migration
...

Best Regards,
Fengguang Wu

--
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:[~2017-03-17  4:06 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
2017-03-17  4:06   ` Fengguang Wu [this message]
2017-03-17 22:48     ` [kbuild-all] " 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=20170317040608.islf67cjbe25rjnx@wfg-t540p.sh.intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --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