From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757865Ab3KHQwE (ORCPT ); Fri, 8 Nov 2013 11:52:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:25093 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757423Ab3KHQwA (ORCPT ); Fri, 8 Nov 2013 11:52:00 -0500 Message-ID: <1383929517.11574.92.camel@deneb.redhat.com> Subject: linux-next build failure From: Mark Salter To: linux-next@vger.kernel.org Cc: linux-kernel , Andrew Morton Date: Fri, 08 Nov 2013 11:51:57 -0500 Organization: Red Hat, Inc Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I'm seeing a build failure for a no-MMU system: mm/built-in.o: In function `__vm_enough_memory': (.text+0x1ce70): undefined reference to `vm_commit_limit' fs/built-in.o: In function `meminfo_proc_show': meminfo.c:(.text+0x6852c): undefined reference to `vm_commit_limit' This patch added vm_commit_limit() to mm/mmap.c, but no-mmu systems use mm/nommu.c instead. commit 50e05119f980037b474043434cb713bf6f859734 Author: Andrew Morton Date: Thu Nov 7 12:01:09 2013 +1100 mm-factor-commit-limit-calculation-fix uninline vm_commit_limit()