From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Jiang Liu <liuj97@gmail.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Jiang Liu <jiang.liu@huawei.com>,
Wen Congyang <wency@cn.fujitsu.com>, Mel Gorman <mgorman@suse.de>,
Minchan Kim <minchan@kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Michal Hocko <mhocko@suse.cz>, Jianguo Wu <wujianguo@huawei.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [RFC PATCH v2, part4 00/39] Simplify mem_init() implementations and kill num_physpages
Date: Mon, 25 Mar 2013 22:37:07 +0530 [thread overview]
Message-ID: <5150843B.1020804@synopsys.com> (raw)
In-Reply-To: <51507916.6030402@gmail.com>
On 03/25/2013 09:49 PM, Jiang Liu wrote:
> Hi James,
> Thanks for reminder, my patch series have been screwed up.
> I will send another version and build a git tree on github.
> Thanks!
> Gerry
Please don't forget conversion of the newly added arc and metag arches !
Thx,
-Vineet
> On 03/24/2013 04:11 PM, James Bottomley wrote:
>> On Sun, 2013-03-24 at 15:24 +0800, Jiang Liu wrote:
>>> The original goal of this patchset is to fix the bug reported by
>>> https://bugzilla.kernel.org/show_bug.cgi?id=53501
>>> Now it has also been expanded to reduce common code used by memory
>>> initializion.
>>>
>>> This is the last part, previous three patch sets could be accessed at:
>>> http://marc.info/?l=linux-mm&m=136289696323825&w=2
>>> http://marc.info/?l=linux-mm&m=136290291524901&w=2
>>> http://marc.info/?l=linux-mm&m=136345342831592&w=2
>>>
>>> This patchset applies to
>>> https://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git since-3.8
>>
>> You're going to have to have a git tree for this if you want this series
>> testing on other architectures. Plus cc'ing linux-arch would be a good
>> idea for that case. The patch series seems to be screwed up in the
>> numbering: The parisc patches 26/39 and 27/39 are identical.
>>
>> James
>>
>>
>>
>>
>>
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
prev parent reply other threads:[~2013-03-25 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1364109934-7851-1-git-send-email-jiang.liu@huawei.com>
2013-03-24 7:24 ` [RFC PATCH v2, part4 01/39] vmlinux.lds: add comments for global variables and clean up useless declarations Jiang Liu
2013-03-24 7:24 ` Jiang Liu
2013-03-24 9:47 ` Arnd Bergmann
2013-03-24 9:47 ` Arnd Bergmann
[not found] ` <1364112719.1975.4.camel@dabdike.int.hansenpartnership.com>
[not found] ` <51507916.6030402@gmail.com>
2013-03-25 17:07 ` Vineet Gupta [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=5150843B.1020804@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=jiang.liu@huawei.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=minchan@kernel.org \
--cc=rientjes@google.com \
--cc=wency@cn.fujitsu.com \
--cc=wujianguo@huawei.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).