Re: [v2,1/2] refactor code parsing size based on memory range

2016-07-19 Thread Hari Bathini
Ping.. On Friday 24 June 2016 10:45 PM, Hari Bathini wrote: On 06/24/2016 10:56 AM, Michael Ellerman wrote: On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote: Currently, crashkernel parameter supports the below syntax to parse size based on memory range: crashkernel=:[,:,...]

Re: [v2,1/2] refactor code parsing size based on memory range

2016-07-05 Thread Hari Bathini
On 07/05/2016 10:48 AM, Michael Ellerman wrote: On 06/24/2016 10:56 AM, Michael Ellerman wrote: On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote: ... While the code is moved to kernel/params.c file, there is no change in logic for crashkernel parameter parsing as the moved code is

Re: [v2,1/2] refactor code parsing size based on memory range

2016-07-04 Thread Michael Ellerman
> On 06/24/2016 10:56 AM, Michael Ellerman wrote: >> On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote: ... > While the code is moved to kernel/params.c file, there is no change in logic > for crashkernel parameter parsing as the moved code is invoked with function > calls at appropriate

Re: [v2,1/2] refactor code parsing size based on memory range

2016-06-24 Thread Hari Bathini
On 06/24/2016 10:56 AM, Michael Ellerman wrote: On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote: Currently, crashkernel parameter supports the below syntax to parse size based on memory range: crashkernel=:[,:,...] While such parsing is implemented for crashkernel parameter,

Re: [v2,1/2] refactor code parsing size based on memory range

2016-06-23 Thread Michael Ellerman
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote: > Currently, crashkernel parameter supports the below syntax to parse size > based on memory range: > > crashkernel=:[,:,...] > > While such parsing is implemented for crashkernel parameter, it applies to > other parameters with