Re: [PATCH next] zram: __zram_reset_device() can be static

On Sat, Feb 09, 2013 at 03:03:28PM +0900, Minchan Kim wrote: > Hi Greg, > > On Fri, Feb 8, 2013 at 11:58 AM, Greg Kroah-Hartman > wrote: > > On Fri, Feb 08, 2013 at 11:47:57AM +0900, Minchan Kim wrote: > >> Hi Fengguang, > > > > Please don't top-post. > > > >> Greg said he doesn't accept any z* f

Re: [PATCH next] zram: __zram_reset_device() can be static

Hi Greg, On Fri, Feb 8, 2013 at 11:58 AM, Greg Kroah-Hartman wrote: > On Fri, Feb 08, 2013 at 11:47:57AM +0900, Minchan Kim wrote: >> Hi Fengguang, > > Please don't top-post. > >> Greg said he doesn't accept any z* friends patches in staging excpet >> plain bug fix and promotion patches until pro

RE: [PATCH 6/6] Drivers: hv: Execute shutdown in a thread context

> -Original Message- > From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org] > Sent: Friday, February 08, 2013 7:44 PM > To: KY Srinivasan > Cc: Jiri Kosina; o...@aepfle.de; jasow...@redhat.com; linux- > ker...@vger.kernel.org; james.bottom...@hansenpartnership.com; > a...@

Re: [PATCH 6/6] Drivers: hv: Execute shutdown in a thread context

On Sat, Feb 09, 2013 at 12:31:49AM +, KY Srinivasan wrote: > > > > -Original Message- > > From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org] > > Sent: Thursday, January 24, 2013 12:18 PM > > To: KY Srinivasan > > Cc: Jiri Kosina; o...@aepfle.de; jasow...@redhat.com;

RE: [PATCH 6/6] Drivers: hv: Execute shutdown in a thread context

> -Original Message- > From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org] > Sent: Thursday, January 24, 2013 12:18 PM > To: KY Srinivasan > Cc: Jiri Kosina; o...@aepfle.de; jasow...@redhat.com; linux- > ker...@vger.kernel.org; james.bottom...@hansenpartnership.com; > a..

staging tree now closed for 3.9

Hi all, With the release of the 3.8-rc7 kernel, I think it's time to close the staging tree for new features / cleanups for 3.9. So I'm closing my tree, and will only be applying obvious bugfixes or regressions to it until 3.9-rc1 comes out. You can keep sending me patches for the tree that don'

[PATCH 0/2] Drivers: hv: balloon

Make furher adjustments to memory pressure reporting and computation. In the current code, we begin to report pressure soon after the balloon driver loads and typically report a very low pressure until the system is fully operational. To avoid having the host take memory balancing decisions on data

[PATCH 2/2] Drivers: hv: balloon: Prevent the host from ballooning the guest too low

Based on the amount of memory being managed set a floor on how low the guest can be ballooned. Signed-off-by: K. Y. Srinivasan Reviewed-by: Haiyang Zhang --- drivers/hv/hv_balloon.c | 35 ++- 1 files changed, 34 insertions(+), 1 deletions(-) diff --git a/drive

[PATCH 1/2] Drivers: hv: balloon: Add a parameter to delay pressure reporting

Delay reporting memory pressure by a specified amount of time. This addresses the problem where the host may take memory balancing decisions based on incorrect memory pressure data that will be posted as soon as the balloon driver is loaded. Signed-off-by: K. Y. Srinivasan Reviewed-by: Haiyang Zh

[PATCH 2/6] staging: xgifb: XGI_GetVBInfo(): delete IF_DEF_LVDS check

Delete IF_DEF_LVDS check, this function is never called when it's true. Signed-off-by: Aaro Koskinen --- drivers/staging/xgifb/vb_setmode.c | 104 1 file changed, 35 insertions(+), 69 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/s

[PATCH 1/6] staging: xgifb: XGI_GetVCLK2Ptr(): delete IF_DEF_LVDS check

Delete IF_DEF_LVDS check, this function is never called when it's true. Signed-off-by: Aaro Koskinen --- drivers/staging/xgifb/vb_setmode.c | 71 +++- 1 file changed, 30 insertions(+), 41 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/s

[PATCH 5/6] staging: xgifb: XGI_GetCRT2ResInfo(): delete IF_DEF_LVDS check

Delete IF_DEF_LVDS check, this function is never called when it's true. Signed-off-by: Aaro Koskinen --- drivers/staging/xgifb/vb_setmode.c | 48 +--- 1 file changed, 23 insertions(+), 25 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/s

[PATCH 3/6] staging: xgifb: XGI_GetTVInfo(): delete IF_DEF_LVDS checks

This function is never called when pVBInfo->IF_DEF_LVDS is true, so we can remove checks and reduce complexity. Signed-off-by: Aaro Koskinen --- drivers/staging/xgifb/vb_setmode.c | 47 +++- 1 file changed, 19 insertions(+), 28 deletions(-) diff --git a/drivers

[PATCH 6/6] staging: xgifb: XGI_SetDelayComp(): delete IF_DEF_LVDS check

Delete IF_DEF_LVDS check, this function is never called when it's true. Signed-off-by: Aaro Koskinen --- drivers/staging/xgifb/vb_setmode.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/staging/xgifb/vb_setmode.c index 2f90464..3d5

[PATCH 4/6] staging: xgifb: XGI_GetLCDInfo(): delete IF_DEF_LVDS check

Delete IF_DEF_LVDS check, this function is never called when it's true. Signed-off-by: Aaro Koskinen --- drivers/staging/xgifb/vb_setmode.c | 27 --- 1 file changed, 12 insertions(+), 15 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/staging/xg

Re: [PATCH] mfd:rtsx: Fix issue that booting OS with SD card inserted

Hi Wei, On Fri, Feb 08, 2013 at 03:24:27PM +0800, wei_w...@realsil.com.cn wrote: > From: Wei WANG > > Realtek card reader supports both SD and MS card. According to the > settings of rtsx MFD driver, SD host will be probed before MS host. > If we boot/reboot Linux with SD card inserted, the rese

[PATCH 2/2] staging: dgrp: prefix function names with dgrp_ in dgrp_specproc.c

Prefix the functions in dgrp_specproc.c to avoid ambiguity in backtraces, such as the "info_proc_open" in this one: unreferenced object 0x88003b6696e0 (size 32): comm "cat", pid 2321, jiffies 4294705179 (age 29.434s) hex dump (first 32 bytes): 40 79 1c 81 ff ff ff ff 60 79 1c 81 ff ff

[PATCH 1/2] staging: dgrp: use correct release op for /proc/dgrp/info

Trinity (the syscall fuzzer) discovered that reading /proc/dgrp/info was leaking some memory. Fix by using the correct release op in info_proc_file_ops. unreferenced object 0x88003b6696e0 (size 32): comm "cat", pid 2321, jiffies 4294705179 (age 29.434s) hex dump (first 32 bytes): 40 79