From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thierry Reding Subject: linux-next: build failure after merge of the mips tree Date: Mon, 7 Oct 2013 17:18:44 +0200 Message-ID: <1381159127-11067-2-git-send-email-treding@nvidia.com> References: <1381159127-11067-1-git-send-email-treding@nvidia.com> Return-path: In-Reply-To: <1381159127-11067-1-git-send-email-treding@nvidia.com> Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-subscribe: List-owner: List-post: List-archive: To: Greg Ungerer , Ralf Baechle , Ashok Kumar Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@linux-mips.org List-Id: linux-next.vger.kernel.org Today's linux-next merge fails to build on various default configuration builds. This seems to be caused by the following commit: 5395d97 MIPS: Fix start of free memory when using initrd Looking at the patchwork URLs in that commit message, Greg's original patch seems to have been fine, but Ashok's patch uses the initrd_end symbol outside of the section protected by an CONFIG_BLK_DEV_INITRD #ifdef and therefore causes to fail during linking. I've reverted the patch in today's linux-next tree. Thierry