From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>, Rusty Russell <rusty@rustcorp.com.au>
Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Zachary Amsden <zach@vmware.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Xiao Guangrong <xiaooguangrong@cn.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: reservetop fix disables mem=
Date: Fri, 28 Aug 2009 12:28:50 -0700 [thread overview]
Message-ID: <4A982FF2.8040001@kernel.org> (raw)
In-Reply-To: <20090824182713.GB9785@elte.hu>
Ingo Molnar wrote:
>> and according to
>> http://lkml.org/lkml/2008/12/10/388
>> http://lkml.org/lkml/2008/12/10/456
>>
>> Zachary should split reserve_top_address() to two functions...
>> before sending that patch to Linus
>
> mind looking at this yourself if interested? Zachary has not been
> active for quite some time.
>
other ways is to revive the Rusty Russell's patchset that move paramater early...
YH
next prev parent reply other threads:[~2009-08-28 19:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 16:45 linux-next: reservetop fix disables mem= Hugh Dickins
2009-08-24 17:38 ` Yinghai Lu
2009-08-24 18:27 ` Ingo Molnar
2009-08-28 19:28 ` Yinghai Lu [this message]
2009-09-06 6:56 ` Yinghai Lu
2009-09-16 0:23 ` Hugh Dickins
2009-09-19 17:55 ` Ingo Molnar
2009-09-19 18:02 ` Yinghai Lu
2009-09-19 18:07 ` Yinghai Lu
2009-09-19 18:32 ` Ingo Molnar
2009-09-19 18:33 ` [tip:x86/urgent] Revert 'x86: Fix system crash when loading with "reservetop" parameter' tip-bot for Yinghai Lu
2009-08-26 1:13 ` linux-next: reservetop fix disables mem= Xiao Guangrong
2009-09-01 7:55 ` [RFC][PATCH] x86: introduce parse_early_param_alone() to parse param early (Was Re: linux-next: reservetop fix disables mem= ) Xiao Guangrong
2009-09-01 15:17 ` Américo Wang
2009-09-03 6:04 ` Xiao Guangrong
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=4A982FF2.8040001@kernel.org \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
--cc=xiaooguangrong@cn.fujitsu.com \
--cc=zach@vmware.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