public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Michal Simek <michal.simek@petalogix•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: microblaze FAULT: memblock: Introduce for_each_memblock() and new accessors, and use it
Date: Mon, 02 Aug 2010 12:25:42 +0200	[thread overview]
Message-ID: <4C569D26.1000907@petalogix.com> (raw)

Hi Ben,

your commit 53e16bfaf19346f59b3502e207aa66c61332075c in linux-next
breaks microblaze kernel compilation. It is easy to remove. Patch is 
below. Please add this change to your commit.

Thanks,
Michal

diff --git a/arch/microblaze/mm/init.c b/arch/microblaze/mm/init.c
index 10bae6e..840026c 100644
--- a/arch/microblaze/mm/init.c
+++ b/arch/microblaze/mm/init.c
@@ -143,7 +143,7 @@ void __init setup_memory(void)

         /* reserve allocate blocks */
         for_each_memblock(reserved, reg) {
-               pr_debug("reserved %d - 0x%08x-0x%08x\n", i,
+               pr_debug("reserved - 0x%08x-0x%08x\n",
                          (u32) reg->base, (u32) reg->size);
                 reserve_bootmem(reg->base, reg->size, BOOTMEM_DEFAULT);
         }


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663

next             reply	other threads:[~2010-08-02 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 10:25 Michal Simek [this message]
2010-08-02 21:20 ` microblaze FAULT: memblock: Introduce for_each_memblock() and new accessors, and use it Benjamin Herrenschmidt

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:10bae6e dfblob:840026c )
 OR (
bs:"microblaze FAULT: memblock: Introduce for_each_memblock() and new accessors, and use it" )
	(help)

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=4C569D26.1000907@petalogix.com \
    --to=michal.simek@petalogix$(echo .)com \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox