On Thu, 11 Aug 2011 08:35:50 +0800 Peng Tao wrote: > On Thu, Aug 11, 2011 at 3:23 AM, Randy Dunlap <rdunlap@xxxxxxxxxxxx> wrote: > > When CONFIG_BLOCK is not enabled (x86_64): > > > > warning: (NFS_V4_1) selects MD which has unmet direct dependencies (BLOCK) > MD depends on BLOCK but when MD is selected, it will not select BLOCK. > Selecting BLOCK at NFS_V4_1 can solve this but it's like resolving > dependency from top down. > > Is MD designed to not be selected from the first place? If not, can we > change it to selecting BLOCK? Hopefully MD will not select BLOCK. The blocklayout parts of NVS_V4_1 could depend on BLOCK. or all of NVS_V4_1 can depend on BLOCK. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
