Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933772Ab0HFFPf (ORCPT ); Fri, 6 Aug 2010 01:15:35 -0400 Received: from e23smtp08.au.ibm.com ([202.81.31.141]:59756 "EHLO e23smtp08.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755878Ab0HFFPa (ORCPT ); Fri, 6 Aug 2010 01:15:30 -0400 From: Benjamin Herrenschmidt To: linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org, torvalds@linux-foundation.org Subject: memblock updates Date: Fri, 6 Aug 2010 15:14:41 +1000 Message-Id: <1281071724-28740-1-git-send-email-benh@kernel.crashing.org> X-Mailer: git-send-email 1.7.0.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1397 Lines: 34 Hi folks ! Here's my current branch. This time build tested on sparc(64), arm, powerpc and sh. I don't have a microblaze compiler at hand. Not much difference from the previous one. Off the top of my head: - Added the memblock_is_region_reserved() fix at the beginning (I'll send that to Linus separately if we decide this series shouldn't go in 2.6.36) - Split the patch adding the new accessors into separate patches for adding the accessors, converting each arch, and removing the old accessors. This makes it clearer, easier to review, etc... I added a couple new accessors for ARM. - Added the ARM updates based on what's upstream now (involves new memblock_is_memory() and memblock_is_memory_region() for use by ARM, nothing fancy there). So very little changes. I haven't changed the init sections so the warnings reported by Steven are still there. I will fix them as an addon patch as I don't believe there's any actual breakage. Now, what do you guys want to do with this now ? I can ask Linus to pull now or we can wait until the end of the merge window and put it into -next for another round... Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/