On Wed, Jul 27, 2022 at 8:34 PM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Wed, 27 Jul 2022 11:17:20 -0700 Suren Baghdasaryan <surenb@xxxxxxxxxx> wrote: > > > > The patch titled > > > Subject: mm: delete unused MMF_OOM_VICTIM flag > > > has been added to the -mm mm-unstable branch. Its filename is > > > mm-delete-unused-mmf_oom_victim-flag.patch > > > > I can't find this and the accompanying patch > > (https://lore.kernel.org/all/20220601213748.DAF1DC385A5@xxxxxxxxxxxxxxx/ > > and https://lore.kernel.org/all/20220601213751.9305CC385A5@xxxxxxxxxxxxxxx/) > > in any tree now and can't find any notifications about them being > > dropped. Could you please check what happened to them? I remember > > there was a minor conflict with maple-tree patchset that we resolved, > > so maybe they are queued together? > > Yesterday I removed the mapletree patchset from mm-unstable, as it > isn't suitable for the next merge window. > > Three other series were significantly dependent on mapletree: > > Refactor of vma_merge and new merge call > > mm: drop oom code from exit_mmap > mm: delete unused MMF_OOM_VICTIM flag > > Refactor of vma_merge and new merge call > > and the single patch > > mm/mlock: drop dead code in count_mm_mlocked_page_nr() > > None of these are very urgent and I might hold them over until > mapletree is reintroduced. This is the lowest risk approach. Got it. No problem, just wanted to make sure they are not abandoned. Thanks! > > I need to revisit these patches to see if they can be reworked for a 5.20-rc1 > with acceptable risk at this late stage. > >
