On Tue, Jan 07, 2014 at 06:17:15AM -0800, Greg KH wrote: > On Tue, Jan 07, 2014 at 02:00:35PM +0000, Mel Gorman wrote: > > A number of NUMA balancing patches were tagged for -stable but I got a > > number of rejected mails from either Greg or his robot minion. The list > > of relevant patches is > > > > FAILED: patch "[PATCH] mm: numa: serialise parallel get_user_page against THP" > > FAILED: patch "[PATCH] mm: numa: call MMU notifiers on THP migration" > > MERGED: Patch "mm: clear pmd_numa before invalidating" > > FAILED: patch "[PATCH] mm: numa: do not clear PMD during PTE update scan" > > FAILED: patch "[PATCH] mm: numa: do not clear PTE for pte_numa update" > > MERGED: Patch "mm: numa: ensure anon_vma is locked to prevent parallel THP splits" > > MERGED: Patch "mm: numa: avoid unnecessary work on the failure path" > > MERGED: Patch "sched: numa: skip inaccessible VMAs" > > FAILED: patch "[PATCH] mm: numa: clear numa hinting information on mprotect" > > FAILED: patch "[PATCH] mm: numa: avoid unnecessary disruption of NUMA hinting during" > > Patch "mm: fix TLB flush race between migration, and change_protection_range" > > Patch "mm: numa: guarantee that tlb_flush_pending updates are visible before page table updates" > > FAILED: patch "[PATCH] mm: numa: defer TLB flush for THP migration as long as" > > > > Fixing the rejects one at a time may cause other conflicts due to ordering > > issues. Instead, this patch series against 3.12.6 is the full list of > > backported patches in the expected order. Greg, unfortunately this means > > you may have to drop some patches already in your stable tree and reapply > > but on the plus side they should be then in the correct order for bisection > > purposes and you'll know I've tested this combination of patches. > > Many thanks for these, I'll go queue them up in a bit and drop the > others to ensure I got all of this correct. Ok, I've now queued all of these up, in this order, so we should be good. I'll do a -rc2 in a bit as it needs some testing. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html