Subject: [merged] documentation-memory-hotplugtxt-fix-typo.patch removed from -mm tree To: qiuxishi@xxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx From: akpm@xxxxxxxxxxxxxxxxxxxx Date: Wed, 28 Aug 2013 13:52:27 -0700 The patch titled Subject: Documentation/memory-hotplug.txt: fix typo has been removed from the -mm tree. Its filename was documentation-memory-hotplugtxt-fix-typo.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Xishi Qiu <qiuxishi@xxxxxxxxxx> Subject: Documentation/memory-hotplug.txt: fix typo Signed-off-by: Xishi Qiu <qiuxishi@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/memory-hotplug.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN Documentation/memory-hotplug.txt~documentation-memory-hotplugtxt-fix-typo Documentation/memory-hotplug.txt --- a/Documentation/memory-hotplug.txt~documentation-memory-hotplugtxt-fix-typo +++ a/Documentation/memory-hotplug.txt @@ -163,7 +163,7 @@ a recent addition and not present on old at read: contains online/offline state of memory. at write: user can specify "online_kernel", "online_movable", "online", "offline" command - which will be performed on al sections in the block. + which will be performed on all sections in the block. 'phys_device' : read-only: designed to show the name of physical memory device. This is not well implemented now. 'removable' : read-only: contains an integer value indicating _ Patches currently in -mm which might be from qiuxishi@xxxxxxxxxx are linux-next.patch mm-hotplug-remove-unnecessary-bug_on-in-__offline_pages.patch mm-use-zone_end_pfn-instead-of-zone_start_pfnspanned_pages.patch mm-use-zone_end_pfn-instead-of-zone_start_pfnspanned_pages-fix.patch mm-use-zone_is_empty-instead-of-ifzone-spanned_pages.patch mm-use-zone_is_initialized-instead-of-ifzone-wait_table.patch kexec-remove-unnecessary-return.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html