From: Tejun Heo <tj@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: status of the memblock tree
Date: Wed, 28 Aug 2013 08:28:09 -0400 [thread overview]
Message-ID: <20130828122809.GC18348@mtj.dyndns.org> (raw)
In-Reply-To: <20130828163459.3eb7fc0d7ae531494f605831@canb.auug.org.au>
Hey, Stephen.
On Wed, Aug 28, 2013 at 04:34:59PM +1000, Stephen Rothwell wrote:
> I was wondering if the memblock tree needs to exist any more. The last
> commit to it was in December 2011 and was merged into Linus' tree during
> the v3.3 merge window.
After the rewrite was complete, the tree was never used. I think it
can be put to rest now. Ingo is routing all memblock changes now.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-08-28 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 6:34 linux-next: status of the memblock tree Stephen Rothwell
2013-08-28 12:28 ` Tejun Heo [this message]
2013-08-29 0:37 ` Stephen Rothwell
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=20130828122809.GC18348@mtj.dyndns.org \
--to=tj@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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