From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Ralph Campbell <rcampbell@nvidia.com>
To: <linux-mm@kvack.org>
Cc: <linux-kernel@vger.kernel.org>, Ralph Campbell <rcampbell@nvidia.com>,
Cc: stable@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] mm/migrate: initialize pud_entry in migrate_vma()
Date: Sat, 20 Jul 2019 12:23:33 +0000 [thread overview]
Message-ID: <20190720122334.24ECD2183E@mail.kernel.org> (raw)
In-Reply-To: <20190719233225.12243-1-rcampbell@nvidia.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 8763cb45ab96 mm/migrate: new memory migration helper for use with device memory.
The bot has tested the following trees: v5.2.1, v5.1.18, v4.19.59, v4.14.133.
v5.2.1: Build OK!
v5.1.18: Build OK!
v4.19.59: Failed to apply! Possible dependencies:
41b4deeaa123 ("RDMA/umem: Make ib_umem_odp into a sub structure of ib_umem")
597ecc5a0954 ("RDMA/umem: Get rid of struct ib_umem.odp_data")
5d6527a784f7 ("mm/mmu_notifier: use structure for invalidate_range_start/end callback")
ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2")
b5231b019d76 ("RDMA/umem: Use ib_umem_odp in all function signatures connected to ODP")
c9990ab39b6e ("RDMA/umem: Move all the ODP related stuff out of ucontext and into per_mm")
d4b4dd1b9706 ("RDMA/umem: Do not use current->tgid to track the mm_struct")
v4.14.133: Failed to apply! Possible dependencies:
155494dbbbf4 ("drm/amdgpu: Update kgd2kfd_shared_resources for dGPU support")
179c02fe90a4 ("drm/tve200: Add new driver for TVE200")
1b0c0f9dc5ca ("drm/amdgpu: move userptr BOs to CPU domain during CS v2")
1b1f42d8fde4 ("drm: move amd_gpu_scheduler into common location")
1ed3d2567c80 ("drm/amdgpu: keep the MMU lock until the update ends v4")
3fe89771cb0a ("drm/amdgpu: stop reserving the BO in the MMU callback v3")
4c660c8fbbf7 ("drm/amdgpu: Add submit IB function for KFD")
528e083d85bd ("drm/amdgpu: rename rmn to amn in the MMU notifier code (v2)")
60de1c1740f3 ("drm/amdgpu: use a rw_semaphore for MMU notifiers")
8cce58fe698a ("drm/amd: add new interface to query cu info")
93065ac753e4 ("mm, oom: distinguish blockable mode for mmu notifiers")
9f0a0b41ffcc ("drm/amdgpu: Add support for reporting VRAM usage")
a216ab09955d ("drm/amdgpu: fix userptr put_page handling")
a46a2cd103a8 ("drm/amdgpu: Add GPUVM memory management functions for KFD")
ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2")
b72cf4fca2bb ("drm/amdgpu: move taking mmap_sem into get_user_pages v2")
ca666a3c298f ("drm/amdgpu: stop using BO status for user pages")
d8d019ccffb8 ("drm/amdgpu: Add KFD eviction fence")
e52482dec836 ("drm/amdgpu: Add MMU notifier type for KFD userptr")
ebdebf428ae6 ("drm/amdgpu: add amdgpu interface to query cu info")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-07-20 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 23:32 Ralph Campbell
2019-07-20 2:03 ` John Hubbard
2019-07-20 12:23 ` Sasha Levin [this message]
2019-08-26 15:11 ` Vlastimil Babka
2019-08-26 17:30 ` Ralph Campbell
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=20190720122334.24ECD2183E@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rcampbell@nvidia.com \
/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