Re: [RESEND PATCH v2 1/2] update mem= option's spec according to its implementation

2012-10-19 Thread KOSAKI Motohiro
On Fri, Oct 19, 2012 at 8:52 PM, Wen Congyang wrote: > At 10/20/2012 02:11 AM, KOSAKI Motohiro Wrote: >> On Fri, Oct 19, 2012 at 6:16 AM, wrote: >>> From: Wen Congyang >>> >>> Current mem= implementation seems buggy because specification and >>> implementation doesn't match. Current mem= has be

Re: [RESEND PATCH v2 1/2] update mem= option's spec according to its implementation

2012-10-19 Thread Wen Congyang
At 10/20/2012 02:11 AM, KOSAKI Motohiro Wrote: > On Fri, Oct 19, 2012 at 6:16 AM, wrote: >> From: Wen Congyang >> >> Current mem= implementation seems buggy because specification and >> implementation doesn't match. Current mem= has been working >> for many years and it's not buggy, it works as

Re: [RESEND PATCH v2 1/2] update mem= option's spec according to its implementation

2012-10-19 Thread KOSAKI Motohiro
On Fri, Oct 19, 2012 at 6:16 AM, wrote: > From: Wen Congyang > > Current mem= implementation seems buggy because specification and > implementation doesn't match. Current mem= has been working > for many years and it's not buggy, it works as expected. So > we should update the specification. > >

[RESEND PATCH v2 1/2] update mem= option's spec according to its implementation

2012-10-19 Thread wency
From: Wen Congyang Current mem= implementation seems buggy because specification and implementation doesn't match. Current mem= has been working for many years and it's not buggy, it works as expected. So we should update the specification. Signed-off-by: Wen Congyang Sort-of-tentatively-acked-

Re: [RESEND PATCH v2 1/2] update mem= option's spec

2012-10-11 Thread Wen Congyang
Hi, HPA When do you have time to review this patchset? Thanks Wen Congyang At 10/11/2012 06:38 PM, we...@cn.fujitsu.com Wrote: > From: Wen Congyang > > Current mem= implementation seems buggy because specification and > implementation doesn't match. Current mem= has been working > for many yea

[RESEND PATCH v2 1/2] update mem= option's spec

2012-10-11 Thread wency
From: Wen Congyang Current mem= implementation seems buggy because specification and implementation doesn't match. Current mem= has been working for many years and it's not buggy, it works as expected. So we should update the specification. Signed-off-by: Wen Congyang Sort-of-tentatively-acked-