From: "H. Peter Anvin" <hpa@zytor.com>
To: Tejun Heo <tj@kernel.org>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
benh@kernel.crashing.org, tony.luck@intel.com,
ralf@linux-mips.org, schwidefsky@de.ibm.com,
liqin.chen@sunplusct.com, lethal@linux-sh.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCHSET tip:x86/memblock] memblock: Kill early_node_map[]
Date: Tue, 26 Jul 2011 15:20:04 -0700 [thread overview]
Message-ID: <4E2F3D94.4000401@zytor.com> (raw)
In-Reply-To: <CAOS58YPZLvXKHdy4nSeqNhk71o5hy-o6XQKbohvuUsGMMMirOA@mail.gmail.com>
On 07/26/2011 02:49 PM, Tejun Heo wrote:
> Hello,
>
> On Tue, Jul 26, 2011 at 11:14 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>> it passes test with my x86 64bits setups.
>
> Great, thanks for testing.
>
>> looks like tip/master does not include tip/x86/memblock and tip/x86/mm yet.
>>
>> So tip/x86/memblock, tip/x86/mm will not get into 3.1?
>
> Yeah, I think the whole thing including the last patchset was a bit
> too late for this merge window. These are basically cleanups and
> could possibly cause weird boot regressions, so having enough time in
> -tip before going mainline seems like a good idea to me.
>
It seems a bit scary, so holding this until 3.2 would definitely be my
preference.
-hpa
next prev parent reply other threads:[~2011-07-26 22:24 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 15:35 [PATCHSET tip:x86/memblock] memblock: Kill early_node_map[] Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 01/23] memblock: Make memblock_overlaps_region() static Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 02/23] memblock: Make memblock_{add|remove|free|reserve}() return int and update prototypes Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 03/23] memblock: Use memblock_reserve() in memblock internal functions Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 04/23] memblock: Add __memblock_dump_all() Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 05/23] memblock: Kill sentinel entries at the end of static region arrays Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 06/23] memblock: Kill memblock_init() Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 07/23] memblock: Separate out memblock_isolate_range() from memblock_set_node() Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 08/23] memblock: Reimplement __memblock_remove() using memblock_isolate_range() Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-28 9:43 ` [PATCH UPDATED " Tejun Heo
2011-07-28 9:43 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 09/23] memblock: Make memblock functions handle overflowing range @size Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 10/23] memblock: Reimplement memblock_enforce_memory_limit() using __memblock_remove() Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 11/23] powerpc: Cleanup memblock usage Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 12/23] memblock: Track total size of regions automatically Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 13/23] memblock: s/memblock_analyze()/memblock_allow_resize()/ and update users Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 14/23] memblock: Implement memblock_add_node() Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 15/23] powerpc: Use HAVE_MEMBLOCK_NODE_MAP Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 16/23] sparc: " Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-08-04 9:52 ` Tejun Heo
2011-08-04 9:52 ` Tejun Heo
2011-08-04 10:13 ` David Miller
2011-08-04 10:13 ` David Miller
2011-08-08 12:30 ` [PATCH UPDATED " Tejun Heo
2011-08-08 12:30 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 17/23] SuperH: " Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 18/23] ia64: " Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 19/23] mips: " Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-08-03 16:17 ` Ralf Baechle
2011-08-03 16:17 ` Ralf Baechle
2011-08-03 16:26 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 20/23] s390: " Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 21/23] score: " Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 15:35 ` [PATCH 22/23] memblock: Kill early_node_map[] Tejun Heo
2011-08-08 12:32 ` [PATCH UPDATED " Tejun Heo
2011-08-08 12:32 ` Tejun Heo
2011-07-26 15:35 ` [PATCH " Tejun Heo
2011-07-26 15:35 ` [PATCH 23/23] memblock: Reimplement memblock allocation using reverse free area iterator Tejun Heo
2011-07-26 15:35 ` Tejun Heo
2011-07-26 21:14 ` [PATCHSET tip:x86/memblock] memblock: Kill early_node_map[] Yinghai Lu
2011-07-26 21:49 ` Tejun Heo
2011-07-26 22:20 ` H. Peter Anvin [this message]
2011-07-28 9:41 ` [PATCH 0.5/23] memblock: Fix include breakages caused by 24aa07882b Tejun Heo
2011-07-28 9:41 ` Tejun Heo
2011-08-18 12:00 ` [PATCHSET tip:x86/memblock] memblock: Kill early_node_map[] Tejun Heo
2011-08-18 12:00 ` Tejun Heo
2011-08-18 21:13 ` H. Peter Anvin
2011-08-18 21:13 ` H. Peter Anvin
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=4E2F3D94.4000401@zytor.com \
--to=hpa@zytor.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.chen@sunplusct.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=yhlu.kernel@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;
as well as URLs for NNTP newsgroup(s).