From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: michal.simek@petalogix.com
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: microblaze FAULT: memblock: Introduce for_each_memblock() and new accessors, and use it
Date: Tue, 03 Aug 2010 07:20:30 +1000 [thread overview]
Message-ID: <1280784030.1902.62.camel@pasglop> (raw)
In-Reply-To: <4C569D26.1000907@petalogix.com>
On Mon, 2010-08-02 at 12:25 +0200, Michal Simek wrote:
> 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.
Ooops. It may be too late to rebase, not sure. Ingo, are you sending
that stuff to Linus or are you waiting for me to do so ? In the later
case, I can fold that fix in easily.
Cheers,
Ben.
> 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);
> }
>
>
prev parent reply other threads:[~2010-08-02 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 10:25 microblaze FAULT: memblock: Introduce for_each_memblock() and new accessors, and use it Michal Simek
2010-08-02 21:20 ` Benjamin Herrenschmidt [this message]
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=1280784030.1902.62.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-next@vger.kernel.org \
--cc=michal.simek@petalogix.com \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox