The patch titled Subject: mm/vmalloc: fix comments about vmap_area struct has been removed from the -mm tree. Its filename was mm-vmalloc-fix-comments-about-vmap_area-struct.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Bang Li <libang.linuxer@xxxxxxxxx> Subject: mm/vmalloc: fix comments about vmap_area struct The vmap_area_root should be in the "busy" tree and the free_vmap_area_root should be in the "free" tree. Link: https://lkml.kernel.org/r/20220305011510.33596-1-libang.linuxer@xxxxxxxxx Fixes: 688fcbfc06e4 ("mm/vmalloc: modify struct vmap_area to reduce its size") Signed-off-by: Bang Li <libang.linuxer@xxxxxxxxx> Reviewed-by: Uladzislau Rezki (Sony) <urezki@xxxxxxxxx> Cc: Pengfei Li <lpf.vector@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- include/linux/vmalloc.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/include/linux/vmalloc.h~mm-vmalloc-fix-comments-about-vmap_area-struct +++ a/include/linux/vmalloc.h @@ -80,8 +80,8 @@ struct vmap_area { /* * The following two variables can be packed, because * a vmap_area object can be either: - * 1) in "free" tree (root is vmap_area_root) - * 2) or "busy" tree (root is free_vmap_area_root) + * 1) in "free" tree (root is free_vmap_area_root) + * 2) or "busy" tree (root is vmap_area_root) */ union { unsigned long subtree_max_size; /* in "free" tree */ _ Patches currently in -mm which might be from libang.linuxer@xxxxxxxxx are