Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755100AbZFOKMn (ORCPT ); Mon, 15 Jun 2009 06:12:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752941AbZFOKMf (ORCPT ); Mon, 15 Jun 2009 06:12:35 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:42023 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751611AbZFOKMe (ORCPT ); Mon, 15 Jun 2009 06:12:34 -0400 Date: Mon, 15 Jun 2009 03:12:37 -0700 (PDT) Message-Id: <20090615.031237.16489152.davem@davemloft.net> To: a.beregalov@gmail.com Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org, linux-mm@kvack.org Subject: Re: 2.6.31-rc1: memory initialization warnings on sparc From: David Miller In-Reply-To: References: X-Mailer: Mew version 6.2.51 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 525 Lines: 13 I know about them, I saw these messages too. kmalloc() initialization got moved earlier so large swaths of sparc early initialization need to move from bootmem to kmalloc or similar. It's just a harmless warning as the bootmem code calls kmalloc() if that's available already. -- 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/