From: David Miller <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
Date: Mon, 15 Jun 2009 10:12:37 +0000 [thread overview]
Message-ID: <20090615.031237.16489152.davem@davemloft.net> (raw)
In-Reply-To: <a4423d670906150303o353f598dg4eb7b1f181344d8e@mail.gmail.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <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
Date: Mon, 15 Jun 2009 03:12:37 -0700 (PDT) [thread overview]
Message-ID: <20090615.031237.16489152.davem@davemloft.net> (raw)
In-Reply-To: <a4423d670906150303o353f598dg4eb7b1f181344d8e@mail.gmail.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <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
Date: Mon, 15 Jun 2009 03:12:37 -0700 (PDT) [thread overview]
Message-ID: <20090615.031237.16489152.davem@davemloft.net> (raw)
In-Reply-To: <a4423d670906150303o353f598dg4eb7b1f181344d8e@mail.gmail.com>
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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-06-15 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 10:03 2.6.31-rc1: memory initialization warnings on sparc Alexander Beregalov
2009-06-15 10:03 ` Alexander Beregalov
2009-06-15 10:03 ` Alexander Beregalov
2009-06-15 10:12 ` David Miller [this message]
2009-06-15 10:12 ` David Miller
2009-06-15 10:12 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090615.031237.16489152.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.