The patch titled Remove obsolete CONFIG_RESOURCES_64BIT has been added to the -mm tree. Its filename is remove-obsolete-config_resources_64bit.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: Remove obsolete CONFIG_RESOURCES_64BIT From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> commit 8308c54d7e312f7a03e2ce2057d0837e6fe3843f ("generic: redefine resource_size_t as phys_addr_t") made CONFIG_RESOURCES_64BIT obsolete, but didn't remove it. Remove it. Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/Kconfig | 6 ------ 1 file changed, 6 deletions(-) diff -puN mm/Kconfig~remove-obsolete-config_resources_64bit mm/Kconfig --- a/mm/Kconfig~remove-obsolete-config_resources_64bit +++ a/mm/Kconfig @@ -181,12 +181,6 @@ config MIGRATION example on NUMA systems to put pages nearer to the processors accessing the page. -config RESOURCES_64BIT - bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT && EXPERIMENTAL) - default 64BIT - help - This option allows memory and IO resources to be 64 bit. - config PHYS_ADDR_T_64BIT def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT _ Patches currently in -mm which might be from geert@xxxxxxxxxxxxxx are origin.patch linux-next.patch remove-obsolete-config_resources_64bit.patch fbdev-fix-typo-in-drivers-video-modedbc.patch unaligned-wire-up-trivial-arches-for-new-common-unaligned-header.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