Message ID | 20220408135323.1559401-1-naoya.horiguchi@linux.dev (mailing list archive) |
---|---|
Headers | show |
Series | mm/hwpoison: fix race between hugetlb free/demotion and memory_failure_hugetlb() | expand |
On Fri, 8 Apr 2022 22:53:20 +0900 Naoya Horiguchi <naoya.horiguchi@linux.dev> wrote: > I updated v7 (https://lore.kernel.org/linux-mm/20220407112929.1344748-1-naoya.horiguchi@linux.dev/) > based on the comment from Miaohe Lin. Now I have a few additional patches. > Any comments and suggestions are welcomed. As [1/3] is cc:stable I queued that for 5.18-rcX and the other two patches I queued for 5.19. This plan means that [1/3] will be merged into mainline without the other two patches yet present, which is a combination which you may not have tested. Please confirm that this will be OK?
On Fri, Apr 08, 2022 at 04:47:55PM -0700, Andrew Morton wrote: > On Fri, 8 Apr 2022 22:53:20 +0900 Naoya Horiguchi <naoya.horiguchi@linux.dev> wrote: > > > I updated v7 (https://lore.kernel.org/linux-mm/20220407112929.1344748-1-naoya.horiguchi@linux.dev/) > > based on the comment from Miaohe Lin. Now I have a few additional patches. > > Any comments and suggestions are welcomed. > > As [1/3] is cc:stable I queued that for 5.18-rcX and the other two > patches I queued for 5.19. > > This plan means that [1/3] will be merged into mainline without the > other two patches yet present, which is a combination which you may not > have tested. Please confirm that this will be OK? Yes, the plan is fine to me. I've tested the kernel with all 3 patched, but 2/3 and 3/3 are simple and the effect should be predictable. I'll test only with 1/3 next week. Thanks, Naoya Horiguchi