From: Ralf Baechle <ralf@linux-mips.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 0/2] FLATMEM: allow memory to start at pfn != 0 [take #2]
Date: Wed, 10 Jan 2007 11:20:54 +0000 [thread overview]
Message-ID: <20070110112054.GA6193@linux-mips.org> (raw)
In-Reply-To: <116841864595-git-send-email-fbuihuu@gmail.com>
On Wed, Jan 10, 2007 at 09:44:03AM +0100, Franck Bui-Huu wrote:
> Here's is the second attempt to make this works on your Malta board
> and all other boards that have some data reserved at the start of
> their memories. In these cases the first patchset assumed wrongly that
> the start of the memory was after this reserved area.
>
> Patch 1/2 should work alone now. the kernel should report that your
> mem config is wasting some memory for tracking reserved pages located
> at the start of the mem.
So this series now works for me, both 1/2 along and 1/2 + 2/2 applied.
So I'll drop this into the 2.6.21 queue.
Ralf
next prev parent reply other threads:[~2007-01-10 16:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 8:44 [PATCH 0/2] FLATMEM: allow memory to start at pfn != 0 [take #2] Franck Bui-Huu
2007-01-10 8:44 ` [PATCH 1/2] Setup min_low_pfn/max_low_pfn correctly Franck Bui-Huu
2007-01-10 8:44 ` [PATCH 2/2] FLATMEM: introduce PHYS_OFFSET Franck Bui-Huu
2007-01-10 11:20 ` Ralf Baechle [this message]
2007-01-10 14:52 ` [PATCH 0/2] FLATMEM: allow memory to start at pfn != 0 [take #2] Franck Bui-Huu
2007-03-02 23:45 ` Maxime Bizon
2007-03-05 14:15 ` Franck Bui-Huu
2007-03-05 16:33 ` Maxime Bizon
2007-03-06 21:39 ` Franck Bui-Huu
2007-03-07 13:18 ` Thomas Bogendoerfer
2007-03-07 16:58 ` Maxime Bizon
2007-03-08 9:01 ` Franck Bui-Huu
2007-03-08 8:54 ` Franck Bui-Huu
2007-03-09 13:18 ` peter fuerst
2007-03-09 13:35 ` Franck Bui-Huu
2007-03-10 9:36 ` peter fuerst
2007-03-12 9:47 ` Franck Bui-Huu
2007-03-12 13:03 ` peter fuerst
2007-03-12 17:05 ` Franck Bui-Huu
2007-03-12 20:02 ` peter fuerst
2007-03-13 8:37 ` Franck Bui-Huu
2007-03-18 11:30 ` peter fuerst
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=20070110112054.GA6193@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=vagabon.xyz@gmail.com \
/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