[RFC 4/4] Enable memory allocation through sysfs interface

ize set is zero, the both the allocated region in low and high memory will be released. Signed-off-by: Ronit Halder --- kernel/ksysfs.c | 23 ++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/kernel/ksysfs.c b/kernel/ksysfs.c index e83b264..4cc286d 100644 --

[RFC 3/4] Adding a new kernel configuration to enable the feature

Kernel configuration option added to enable run time memory reservation feature for kexec. Signed-off-by: Ronit Halder --- mm/Kconfig | 6 ++ 1 file changed, 6 insertions(+) diff --git a/mm/Kconfig b/mm/Kconfig index 97a4e06..8b1533d 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -668,3

[RFC 2/4] Functions for memory reservation and release

Functions reserve and release memory from CMA area(s). Signed-off-by: Ronit Halder --- include/linux/kexec.h | 11 ++- kernel/kexec_core.c | 83 +++ 2 files changed, 93 insertions(+), 1 deletion(-) diff --git a/include/linux/kexec.h b

[RFC 1/4] Creating one or two CMA area at Boot time

memory and one in high memory) will be created. Signed-off-by: Ronit Halder --- arch/x86/kernel/setup.c | 44 +--- 1 file changed, 41 insertions(+), 3 deletions(-) diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c index d2bbe34..87c16c7 100644

[RFC 0/4] Kexec: Enable run time memory resrvation of crash kernel

But, the movable pages become unmovable momentarily for pinning. The CMA fails for this reason. I don't have any solution for that right now. This approach will work when the this problems with CMA will be fixed. The patch is enabled by a kernel configuration option CONFIG_KEXEC_CMA. Ronit

Proposal for run time memory allocation for crash kernel

r_err("%s: Error reserving CMA area for crashkernel.\n", __func__); return; } - pr_info("Reserving %ldMB of memory at %ldMB for crashkernel (System RAM: %ldMB)\n", + pr_info("ronit halder Reserving %ldMB of memory at %ldMB for crashkernel (System RAM: %ldMB)\n

[PATCH] Staging: comedi: removing useless init/exit

Removing init and exit functions as they do nothing. Signed-off-by: Ronit Halder --- drivers/staging/comedi/comedi_usb.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/staging/comedi/comedi_usb.c b/drivers/staging/comedi/comedi_usb.c index 9c946d4..ed13bf6 100644 --- a

[PATCH] Staging: rts5208: use dmam_alloc_coherent

This patch replaces dma_alloc_coherent with the corresponding managed interface. Signed-off-by: Ronit Halder --- drivers/staging/rts5208/rtsx.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/staging/rts5208/rtsx.c b/drivers/staging/rts5208/rtsx.c index b4e4543

[PATCH] Staging: fbtft: Use BIT macro

Replace (1 << x) by BIT(x) Signed-off-by: Ronit halder --- drivers/staging/fbtft/fb_ssd1351.c | 4 +-- drivers/staging/fbtft/fbtft.h | 56 +++--- 2 files changed, 30 insertions(+), 30 deletions(-) diff --git a/drivers/staging/fbtft/fb_ssd1351.c b/d

Re: [PATCH] staging: dgap: fix memory leak in dgap_parsefile()

> Why not just reject it earlier instead of allocating more data? I agree on your point. But we have to make different mechanism for that and my patch is only to fix the current code. regards -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to maj

Re: [PATCH] staging: dgap: fix memory leak in dgap_parsefile()

The existing dgap_parsefile() rejects invalid config file. But before we know that config file is invalid a lot of memory leak can happen. Removing the chances of memory leak won't heart anyone. regards, Ronit Halder -- To unsubscribe from this list: send the line "unsubscribe linux-

[PATCH] staging: dgap: fix memory leak in dgap_parsefile()

In dgap_parsefile() char pointers are set with kstrdup() without checking that some string is allocated to that char pointer before. This patch frees the memory if already allocated and then set the poniter with kstrdup(). Signed-off-by: Ronit halder --- drivers/staging/dgap/dgap.c | 12

Re: [PATCH v2 1/2] Staging: wilc1000: Use NULL instead of zero

On Wed, 2015-09-16 at 20:15 -0700, Greg KH wrote: > On Thu, Sep 17, 2015 at 08:28:52AM +0530, roni wrote: > > Sorry for the ambiguity. > > I am talking about my second patch in the series. > > https://lkml.org/lkml/2015/9/15/293 > > > > > > None of the line edited in first patch haven't changed af

Re: [PATCH v2 1/2] Staging: wilc1000: Use NULL instead of zero

Why not the second one? None of the line edited in first patch haven't changed after that. On Tue, Sep 15, 2015 at 7:24 PM, Greg KH wrote: > On Tue, Sep 15, 2015 at 03:04:58PM +0530, Ronit Halder wrote: >> This patch fixes the warning generated by sparse >> "Using plai

[PATCH 2/2] Staging: wilc1000: fix NULL comparison style

Fixed NULL comparison style as suggested by checkpatch.pl with --strict option. Signed-off-by: Ronit halder --- drivers/staging/wilc1000/coreconfigurator.c | 2 +- drivers/staging/wilc1000/linux_wlan.c | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers

[PATCH v2 1/2] Staging: wilc1000: Use NULL instead of zero

This patch fixes the warning generated by sparse "Using plain integer as NULL pointer" by using NULL instead of zero. Signed-off-by: Ronit halder --- v2: added a new patch in this patch series to fix the NULL comparison style drivers/staging/wilc1000/coreconfigura

Re: [PATCH] Staging: wilc1000: Use NULL instead of zero

I checked but it didn't show me any warning. Can you please specify the warning? regards On Mon, Sep 14, 2015 at 2:06 PM, Sudip Mukherjee wrote: > On Mon, Sep 14, 2015 at 11:03:34AM +0530, Ronit Halder wrote: >> This patch fixes the warning generated by sparse >> "Us

[PATCH] Staging: wilc1000: Use NULL instead of zero

This patch fixes the warning generated by sparse "Using plain integer as NULL pointer" by using NULL instead of zero. Signed-off-by: Ronit halder --- drivers/staging/wilc1000/coreconfigurator.c | 14 +++--- drivers/staging/wilc1000/linux_wlan.c | 6 +++--- 2 files c

[PATCH] Staging: most: Use NULL instead of zero

This patch fixes the warning generated by sparse "Using plain integer as NULL pointer" by using NULL instead of zero. Signed-off-by: Ronit halder --- drivers/staging/most/aim-network/networking.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/stagin

Re: [PATCH] Staging: fbtft: Fix iomem dereference

Yes, it is not I/O memory address. I was wrong on that. But it makes sparse happy. Is here any side effect of using ioread16() ? regards, ronit On Tue, Aug 18, 2015 at 2:27 PM, Dan Carpenter wrote: > On Tue, Aug 18, 2015 at 12:16:57PM +0530, Ronit Halder wrote: >> This patch fixes th

[PATCH] Staging: fbtft: Fix iomem dereference

This patch fixes the warning generated by sparse "cast removes address space of expression" by using ioread16 function insted of directly dereferencing I/O memory. Signed-off-by: Ronit halder --- drivers/staging/fbtft/fb_agm1264k-fl.c | 5 +++-- 1 file changed, 3 insertions(+), 2

[PATCH] Staging: lustre: fixed a blank line after declarations coding style issue

Fixed a blank line after declarations coding style issue Signed-off-by: Ronit Halder --- drivers/staging/lustre/lustre/lov/lov_merge.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/lustre/lustre/lov/lov_merge.c b/drivers/staging/lustre/lustre/lov/lov_merge.c index b7e7bfa

[PATCH v2] Staging: android: ion: fixed a blank line after declarations coding style issue

Fixed a coding style issue. Signed-off-by: Ronit Halder --- drivers/staging/android/ion/ion.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c index 6f48112..e44f5e6 100644 --- a/drivers/staging/android/ion/ion.c +++ b

Re: [PATCH] Staging: android: ion: fixed a blank line after declarations coding style issue

On Thu, 2015-07-09 at 11:05 +0530, Sudip Mukherjee wrote: > On Thu, Jul 09, 2015 at 08:20:57AM +0530, rcodin wrote: > > From: Ronit Halder > > You do not need a From: here. Please fix your gitconfig file and > git send-email will give your name correctly in the email header. &g

[PATCH] Staging: android: ion: fixed a blank line after declarations coding style issue

Fixed a coding style issue. Signed-off-by: Ronit Halder --- drivers/staging/android/ion/ion.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c index 6f48112..e44f5e6 100644 --- a/drivers/staging/android/ion/ion.c +++ b