Re: [PATCH 00/46] staging: line6: drop MIDI state sysfs attrs

On Thu, Nov 22, 2012 at 08:48:39PM +0100, Stefan Hajnoczi wrote: > Let's put the line6 staging driver on a diet for Thanksgiving! :) Yeah! > Markus and I have discussed the MIDI processing that currently happens in the > line6 driver. This stuff really belongs in userspace where a library or > u

[PATCH 37/46] staging: line6: drop variax raw sysfs attrs

Note that VARIAX_SYSEX_ACTIVATE was never used so drop it along with the other VARIAX_SYSEX_* constants which are now unused. Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/variax.c | 73 -- 1 file changed, 73 deletions(-) diff --git a/drivers/s

[PATCH 10/10] ASoC: wm8995: Convert to use devm_regmap_init_{spi,i2c}()

Signed-off-by: Tushar Behera --- sound/soc/codecs/wm8995.c | 26 +++--- 1 files changed, 3 insertions(+), 23 deletions(-) diff --git a/sound/soc/codecs/wm8995.c b/sound/soc/codecs/wm8995.c index 2eb68c1..f1a7cf1 100644 --- a/sound/soc/codecs/wm8995.c +++ b/sound/soc/codecs/

[PATCH 35/46] staging: line6: drop variax active sysfs attr

The get_string() function has no other callers so remove it too. Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/variax.c | 36 1 file changed, 36 deletions(-) diff --git a/drivers/staging/line6/variax.c b/drivers/staging/line6/variax.c index 0f1846

[PATCH 34/46] staging: line6: drop variax dump sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/variax.c | 20 1 file changed, 20 deletions(-) diff --git a/drivers/staging/line6/variax.c b/drivers/staging/line6/variax.c index 8eec139..0f1846e 100644 --- a/drivers/staging/line6/variax.c +++ b/drivers/staging/line6

[PATCH 33/46] staging: line6: drop variax bank sysfs attr

The get_string() function is no longer used so drop it too. Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/variax.c | 34 -- drivers/staging/line6/variax.h | 5 - 2 files changed, 39 deletions(-) diff --git a/drivers/staging/line6/variax.c b/driver

[PATCH 32/46] staging: line6: drop variax name sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/variax.c | 27 --- 1 file changed, 27 deletions(-) diff --git a/drivers/staging/line6/variax.c b/drivers/staging/line6/variax.c index 31ece34..94a9f71 100644 --- a/drivers/staging/line6/variax.c +++ b/drivers/stagin

[PATCH] Staging: Android: logger: module_exit implementation

This patch creates the module_exit for the android logger so that it can be loaded and unloaded as a module. The android logger is already declared as a tristate in the Kconfig but the module_exit function was missing. device_initcall works also with modprobe since include/linux/init.h: #define

RE: [PATCH 2/2] mmc: dw_mmc: Handle wp-gpios from device tree

On Thursday, November 22, 2012, Doug Anderson wrote: > On Wed, Nov 21, 2012 at 5:42 PM, Seungwon Jeon wrote: > > Hi, > > > > wp-gpios has been implemented in dw_mmc-exynos.c > > It can be reused for EXYNOS platform? We need to modify some though. > > Yup, I've seen that. Patch 1/2 ("mmc: dw_mmc

Re: [PATCH 1/1] tty: vt: Remove redundant null check before kfree.

On Thu, Nov 22, 2012 at 12:17:00AM +0100, Jiri Slaby wrote: > On 11/22/2012 12:00 AM, Greg KH wrote: > > On Wed, Nov 21, 2012 at 11:43:34PM +0100, Jiri Slaby wrote: > >> On 11/21/2012 03:46 PM, Greg KH wrote: > >>> On Wed, Nov 21, 2012 at 10:49:07AM +0530, Sachin Kamat wrote: > --- a/drivers/t

[PATCH 31/46] staging: line6: drop variax tone sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/variax.c | 42 -- drivers/staging/line6/variax.h | 5 - 2 files changed, 47 deletions(-) diff --git a/drivers/staging/line6/variax.c b/drivers/staging/line6/variax.c index ef78f5a..31ece34 10064

Re: [PATCH] regulator: tps80031: Trivial cleanups

On Thursday 22 November 2012 02:00 PM, Axel Lin wrote: This patch includes below cleanups: - Fix typo in comment - Fix showing wrong register in dev_err - Remove unnecessary rinfo variable - Add TPS80032 to MODULE_DESCRIPTION Signed-off-by: Axel Lin --- Acked-by: Laxman Dewangan -- To unsubs

[PATCH 30/46] staging: line6: drop variax volume sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/variax.c | 42 -- drivers/staging/line6/variax.h | 5 - 2 files changed, 47 deletions(-) diff --git a/drivers/staging/line6/variax.c b/drivers/staging/line6/variax.c index e76255b..ef78f5a 10064

[PATCH 29/46] staging: line6: drop variax model sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/variax.c | 38 -- drivers/staging/line6/variax.h | 5 - 2 files changed, 43 deletions(-) diff --git a/drivers/staging/line6/variax.c b/drivers/staging/line6/variax.c index 8df529f..e76255b 100644 --

[PATCH 00/46] staging: line6: drop MIDI state sysfs attrs

Let's put the line6 staging driver on a diet for Thanksgiving! :) Markus and I have discussed the MIDI processing that currently happens in the line6 driver. This stuff really belongs in userspace where a library or utility can use ALSA MIDI APIs to control the device. Moving MIDI processing to

[PATCH 04/46] staging: line6: drop dirty sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 21 + drivers/staging/line6/pod.h | 5 - 2 files changed, 1 insertion(+), 25 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 8fdbe9f..7c76b65 100644 --- a/drivers/s

[PATCH 10/46] staging: line6: drop name_buf sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 43 --- 1 file changed, 43 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 76525c5..dbf821e 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/st

[PATCH 11/46] staging: line6: drop retrieve_amp_setup sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 14 -- 1 file changed, 14 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index dbf821e..6d6cd5a 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/staging/line6/pod.c @@ -628,16

[PATCH 19/46] staging: line6: drop tuner_note sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 7 --- drivers/staging/line6/pod.h | 5 - 2 files changed, 12 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 3184570..57fbe27 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers

[PATCH 06/10] ASoC: wm8753: Convert to use devm_regmap_init_{spi,i2c}()

Signed-off-by: Tushar Behera --- sound/soc/codecs/wm8753.c | 32 ++-- 1 files changed, 6 insertions(+), 26 deletions(-) diff --git a/sound/soc/codecs/wm8753.c b/sound/soc/codecs/wm8753.c index 9914215..50a5dc7 100644 --- a/sound/soc/codecs/wm8753.c +++ b/sound/soc/c

[PATCH]sched/rt.c: Add reschedule to switched_from_rt()

Reschedule rq->curr if the first RT task has just been pulled to the rq. Signed-off-by: Kirill V Tkhai CC: Steven Rostedt CC: Ingo Molnar CC: Peter Zijlstra --- kernel/sched/rt.c |7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c

Re: [PATCH] bdi: Track users that require stable page writes

On Wed, Nov 21, 2012 at 06:33:43PM -0800, Darrick J. Wong wrote: > How's this look to everyone? No more user-writable flag, and most of the > helper functions are gone. Now fix up the subject line as well and we might have a deal :) > (Are these emails even getting through?) At least this one i

[PATCH 24/46] staging: line6: drop midi_mask_receive

The midi_mask_receive sysfs attribute selects the MIDI channels on which to receive messages. There is no need to do this at the driver level, instead the MIDI application endpoints decide which channels to use. Other drivers don't implement midi_mask_receive so applications cannot make use of thi

[PATCH v2 0/3] charger-manager: Bug fix and split _probe function

This patchset include bug fix patch and code clean to split _probe function because _probe function is longer than 400 line. Dear Anton, The previous patchset is sent from wrong email address because I'm mistake. Please ignore previous patchset. Chanwoo Choi (3): charger-manager: Fix bug relate

[PATCH v2 2/3] charger-manager: Fix bug when check dropped voltage after fullbatt event

This patch check difference value between current voltage of battery and desc->fullbatt_uV whether positve or negative number. If difference value is negative number when current voltage of battery is larger than desc->fullbatt_uV, charger-manager return immediately because battery is fully charged

[PATCH v2 1/3] charger-manager: Fix bug related to checking fully charged state of battery

This patch fix bug related to checking fully charged state of battery when charger-manager call is_full_charged() function. After reading property of charger/fuel-gauge through power_supply API, val.intval is more than 1. So, is_full_charged() function always return true. If true, battery means ful

[PATCH v2 3/3] charger-manager: Split _probe funtion for code clean

This patch split _probe function for readability because _probe function is longer than 400 line. Signed-off-by: Chanwoo Choi Signed-off-by: Myungjoo Ham Signed-off-by: Kyungmin Park --- drivers/power/charger-manager.c | 279 +++ 1 files changed, 168 insert

Re: [RFC 3/3] man-pages: Add man page for vmpressure_fd(2)

On Wed, 21 Nov 2012, Andrew Morton wrote: > The proposed API bugs me a bit. It seems simplistic. I need to have a > quality think about this. Maybe the result of that think will be to > suggest an interface which can be extended in a back-compatible fashion > later on, if/when the simplistic nat

[PATCH 4/4] video: vt8500: Convert to use devm_ioremap()

While at it, fix the return statements. Signed-off-by: Tushar Behera --- drivers/video/vt8500lcdfb.c | 14 -- 1 files changed, 4 insertions(+), 10 deletions(-) diff --git a/drivers/video/vt8500lcdfb.c b/drivers/video/vt8500lcdfb.c index c42f15d..96a955e 100644 --- a/drivers/video/

Re: [PATCH 2/2] mmc: dw_mmc: Handle wp-gpios from device tree

On 11/22/2012 07:03 AM, Doug Anderson wrote: > On some SoCs (like exynos5250) you need to use an external GPIO for > write protect. Add support for wp-gpios to the core dw_mmc driver > since it could be useful across multiple SoCs. > > With this change I am able to make use of the write protect f

Re: [PATCH] exec: do not leave bprm->interp on stack

+-- On Mon, 19 Nov 2012, Kees Cook wrote --+ | I think to avoid the explosion of request_module calls in the abusive | case, we could simply return ELOOP instead of ENOEXEC on max | recursion. -> http://www.spinics.net/lists/mm-commits/msg92433.html 1. returning -ELOOP has a side effect of not r

[PATCH] regulator: tps80031: Trivial cleanups

This patch includes below cleanups: - Fix typo in comment - Fix showing wrong register in dev_err - Remove unnecessary rinfo variable - Add TPS80032 to MODULE_DESCRIPTION Signed-off-by: Axel Lin --- drivers/regulator/tps80031-regulator.c | 10 -- 1 file changed, 4 insertions(+), 6 del

[PATCH 3.6.6 1/3] i82975x_edac: cleanup debug code

Subject: [PATCH 3.6.6 1/3] i82975x_edac: cleanup debug code the patch converts existing debug code to use the edac standard method instead of hardcoded ifdefs. Signed-off-by: Arvind R. --- drivers/edac/i82975x_edac.c | 196 ++ 1 file changed, 105 insertions(+), 9

Re: Re: [PATCH] extcon : callback function to read cable property

On Thu, Nov 22, 2012 at 01:00:52PM +, Tc, Jenny wrote: [...] > For this solution to work, the cable provider itself > need to register with any of these subsystems - > power_supply/regulator/charger manager > IMHO a cable provider shouldn't register itself with any of the subsystem. > > For

Re: [PATCH] [firmware_class] Fix compile with no builtin firmware

On Wed, Nov 21, 2012 at 10:01 PM, Solomon Peachy wrote: > On Wed, Nov 21, 2012 at 09:35:28AM +0800, Ming Lei wrote: >> Solomon, I can't duplicate the build failure with your .config on >> 3.7-rc5-next. > > Okay, so it's since been fixed. > >> > * The #ifdef wraps code that pertains solely to bui

Re: [V2 PATCH 1/3] staging: ozwpan: Remove redundant null check before kfree in ozpd.c

On Wed, Nov 21, 2012 at 05:26:12PM +, Rupesh Gujare wrote: > On 21/11/12 16:19, Dan Carpenter wrote: > >When someone sends a patch there are a several possible responses: > >1) Ack the patch. > >2) Request that the submitter redo it. The downside is that no one > >likes redoing patches. >

Re: [PATCH 2/2] mmc: dw_mmc: Handle wp-gpios from device tree

On Wed, Nov 21, 2012 at 5:42 PM, Seungwon Jeon wrote: > Hi, > > wp-gpios has been implemented in dw_mmc-exynos.c > It can be reused for EXYNOS platform? We need to modify some though. Yup, I've seen that. Patch 1/2 ("mmc: dw_mmc: exynos: Stop claiming wp-gpio") addressed that. For some reason I

Re: [PATCH] staging: dgrp: dgrp_tty.c: Audit the return values of get/put_user()

On Mon, Nov 19, 2012 at 06:38:29PM +0530, Kumar amit mehta wrote: > On Mon, Nov 19, 2012 at 02:15:54PM +0300, Dan Carpenter wrote: > > On Mon, Nov 19, 2012 at 04:25:31PM +0530, Kumar Amit Mehta wrote: > > > -- fix for missing audits for return values of get_user() and put_user(). > > > -- Remove th

[PATCH 22/46] staging: line6: drop finish sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 21 - 1 file changed, 21 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 052db4a..797f6e0 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/staging/line6/pod.c @@ -

Re: [PATCH 00/46] staging: line6: drop MIDI state sysfs attrs

On Thu, Nov 22, 2012 at 8:58 PM, Greg Kroah-Hartman wrote: > On Thu, Nov 22, 2012 at 08:48:39PM +0100, Stefan Hajnoczi wrote: >> Markus and I have discussed the MIDI processing that currently happens in the >> line6 driver. This stuff really belongs in userspace where a library or >> utility can

Re: [PATCH] block: Don't access request after it might be freed

On 2012-11-22 11:00, Roland Dreier wrote: > From: Roland Dreier > > After we've done __elv_add_request() and __blk_run_queue() in > blk_execute_rq_nowait(), the request might finish and be freed > immediately. Therefore checking if the type is REQ_TYPE_PM_RESUME > isn't safe afterwards, because

[PATCH 21/46] staging: line6: drop tuner_pitch sysfs attr

Dropping this final tuner sysfs attr also leaves the POD_GET_SYSTEM_PARAM() macro, pod_get_system_param_string(), and pod_get_system_param_int() unused. Remove them immediately to avoid compiler warnings. POD_monitor_level is now the only SYSEX value that needs to be watched by the driver since t

[PATCH 20/46] staging: line6: drop tuner_mute sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 34 -- drivers/staging/line6/pod.h | 5 - 2 files changed, 39 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 57fbe27..df2f37a 100644 --- a/drivers/stag

[PATCH 18/46] staging: line6: drop tuner_freq sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 8 drivers/staging/line6/pod.h | 5 - 2 files changed, 13 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index f84a4ea..3184570 100644 --- a/drivers/staging/line6/pod.c +++ b/driver

Re: [PATCH 1/4] mfd: ab8500: add devicetree support for fuelgauge

On Fri, Nov 23, 2012 at 12:13:44AM +0530, Rajanikanth H.V wrote: [...] > +/* > + * Note that the batres_vs_temp table must be strictly sorted by falling > + * temperature values to work. > + */ > +struct batres_vs_temp temp_to_batres_tbl_thermistor[] = { It must be static. [..] > +struct batres_v

Re: [PATCH v4 14/14] HID: hid-multitouch: forwards MSC_TIMESTAMP

Hi Guys, well, I'm not very satisfied with this patch. I first thought it was a good idea but I can see now several cons: 1. Henrik would like to partially base the time spent between two events when the device wraps on the *event* time. This is a great idea for consistency, but I'm afraid I won't

drm_gem_create_mmap_offset / intel_uxa_prepare_access bo problems

Hi Chris! Problem: === Slowdown of system, missing icons after 16 days kernel uptime and 12 days Xserver uptime. Xorg log: flooded with "(WW) intel(0): intel_uxa_prepare_access: bo map (use gtt? 1, access 1) failed: No space left on device" lines dmesg: flooded with "[drm:drm_gem_create_mma

[PATCH 16/46] staging: line6: drop store_effects_setup sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 68 - 1 file changed, 68 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index abf7ebe..949b8f7 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/

[PATCH 15/46] staging: line6: drop store_channel sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 14 -- 1 file changed, 14 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index deafee9..abf7ebe 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/staging/line6/pod.c @@ -545,16

[PATCH 14/46] staging: line6: drop store_amp_setup sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 14 -- 1 file changed, 14 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 95769c5..deafee9 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/staging/line6/pod.c @@ -565,16

[PATCH 13/46] staging: line6: drop retrieve_effects_setup sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 48 - 1 file changed, 48 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index bc65fc7..95769c5 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/

[PATCH 12/46] staging: line6: drop retrieve_channel sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 14 -- 1 file changed, 14 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 6d6cd5a..bc65fc7 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/staging/line6/pod.c @@ -608,16

[PATCH 08/46] staging: line6: change monitor_level type ValueWait -> int

The monitor_level sysfs attr has been dropped and we never need to wait on the monitor_level value to change. Switch to a plain int and drop the wait queue. Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 10 +- drivers/staging/line6/pod.h | 2 +- 2 files changed, 6 in

[PATCH 07/46] staging: line6: drop monitor_level sysfs attr

The monitor level can be adjusted using an ALSA volume control. Therefore the sysfs attribute is unnecessary. Note that we leave the monitor_level driver variable so that the ALSA volume control still works. Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 12 1 fil

[PATCH 00/10] ASoC: codec: devm_ related modifications

This patchset includes devm_ related modifications for sound codecs. First 2 patches fix warning for freeing of devm_ allocated data. The next patch introduces usage of devm_kzalloc() in wm8995 codec. Following 7 patches introduce usage of devm_regmap_init_xxx() in remaining codecs. Tushar Behera

Re: [PATCH 00/27] Latest numa/core release, v16

On Wed, 21 Nov 2012, Ingo Molnar wrote: > Btw., what I did was to simply look at David's profile on the > regressing system and I compared it to the profile I got on a > pretty similar (but unfortunately not identical and not > regressing) system. I saw 3 differences: > > - the numa emulation

[PATCH 06/46] staging: line6: drop dump_buf sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 40 1 file changed, 40 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 56eab0a..c1eb145 100644 --- a/drivers/staging/line6/pod.c +++ b/drivers/stagi

[PATCH 01/46] staging: line6: drop channel sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 51 - drivers/staging/line6/pod.h | 5 - 2 files changed, 56 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index 4a86f7a..e3e2247 100644 --- a/d

[PATCH v4 10/12] iommu/exynos: add support for System MMU 3.2 and 3.3

Since System MMU 3.2 and 3.3 have more prefetch buffers than 2, the existing function to set prefetch buffers, exynos_sysmmu_set_prefbuf() is not able to support them. This commit removes exynos_sysmmu_set_prefbuf() and introduces new interface, exynos_sysmmu_set_pbuf() that can pass information of

Re: i915: black screen after blank when LID is closed on Linux >= 3.1

Hi, Thanks for the report. Now this smells like something which could take a bit longer to track down, so can you please file this on bugs.freedesktop.org against DRM -> DRI/Intel to ensure that we dont' loose track of it? A few questions and things to test below. On Thu, Nov 22, 2012 at 7:54 PM

Re: [PATCH v3 11/12] x86, boot: add fields to support load bzImage and ramdisk high

On Thu, Nov 22, 2012 at 10:51 AM, H. Peter Anvin wrote: > On 11/22/2012 10:50 AM, Yinghai Lu wrote: >> >> >> ok, I will use 0xc0 instead, and at the same time try to fix that from >> kexec. >> >> then user will still have chance to use old kexec tools without enable >> CONFIG_EFI_STUB in kernel. >

Re: [PATCHv9 1/3] Runtime Interpreted Power Sequences

On Wed, Nov 21, 2012 at 2:31 AM, Mark Brown wrote: > As I said in my earlier reviews I think this is a useful thing to have > as a utility library for drivers independantly of the DT bindings, it > would allow drivers to become more data driven. Perhaps we can rework > the series so that the DT

[PATCH 05/10] ASoC: wm8741: Convert to use devm_regmap_init_{spi,i2c}()

Signed-off-by: Tushar Behera --- sound/soc/codecs/wm8741.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/soc/codecs/wm8741.c b/sound/soc/codecs/wm8741.c index 4281a08..99b8ebe 100644 --- a/sound/soc/codecs/wm8741.c +++ b/sound/soc/codecs/wm8741.c @@ -522,7 +522

[PATCH 02/46] staging: line6: drop clip sysfs attr

Signed-off-by: Stefan Hajnoczi --- drivers/staging/line6/pod.c | 23 --- drivers/staging/line6/pod.h | 5 - 2 files changed, 28 deletions(-) diff --git a/drivers/staging/line6/pod.c b/drivers/staging/line6/pod.c index e3e2247..4abe2de 100644 --- a/drivers/staging/line6/p

[PATCH v4 09/12] iommu/exynos: add support for runtime pm and suspend/resume

This change enables the client device drivers not to care about the state of System MMU since the internal state of System MMU is controlled by the runtime PM and suspend/resume callback functions. Signed-off-by: KyongHo Cho --- drivers/iommu/exynos-iommu.c | 175 ++--

Re: [PATCH v3 11/12] x86, boot: add fields to support load bzImage and ramdisk high

On 11/22/2012 12:18 PM, Yinghai Lu wrote: > for kexec bzImage --real-mode-entry, code after setup_header will be executed. For real mode entry we go through the real mode path which takes care of this. What matters is the 32/64-bit entry point. -hpa -- H. Peter Anvin, Intel Open S

[PATCH 32/40] mm: numa: Rate limit the amount of memory that is migrated between nodes

NOTE: This is very heavily based on similar logic in autonuma. It should be signed off by Andrea but because there was no standalone patch and it's sufficiently different from what he did that the signed-off is omitted. Will be added back if requested. If a large number of

Re: [PATCH] tty: Add driver unthrottle in ioctl(...,TCFLSH,..).

On 22.11.2012 4:47, andrew mcgregor wrote: On 11/22/2012 at 10:39 AM, in message <50ad4a01.7060...@ilyx.ru>, Ilya Zykov wrote: On 22.11.2012 1:30, Alan Cox wrote: Function reset_buffer_flags() also invoked during the ioctl(...,TCFLSH,..). At the time of request we can have full buffers and

Re: [PATCH 00/46] Automatic NUMA Balancing V4

On Thu, Nov 22, 2012 at 12:27:15AM +0100, Ingo Molnar wrote: > > * Mel Gorman wrote: > > > > I did a quick SPECjbb 32-warehouses run as well: > > > > > > numa/core balancenuma-v4 > > > SPECjbb +THP: 655 k/sec 607 k/sec > > > > > >

[PATCH 2/4] staging/rtl8187se: Remove an unnecessary line continuation in r8180_core.c

The following warnings fixed. - WARNING: Avoid unnecessary line continuations Signed-off-by: YAMANE Toshiaki --- drivers/staging/rtl8187se/r8180_core.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/drivers/staging/rtl8187se/r8180_core.c b/drivers/staging/rtl81

Re: [PATCH 000/493] remove CONFIG_HOTPLUG as an option

Grant Likely writes: > > You mean this series wasn't created with a script? You did this by > hand? If so then I must say kudos on your dedication! > > But it makes me more nervous about the series. Too easy to fat > finger many things when touching that many files. > No, I didn't do them by hand

[PATCH 10/40] mm: compaction: Add scanned and isolated counters for compaction

Compaction already has tracepoints to count scanned and isolated pages but it requires that ftrace be enabled and if that information has to be written to disk then it can be disruptive. This patch adds vmstat counters for compaction called compact_migrate_scanned, compact_free_scanned and compact_

[PATCH 16/40] mm: mempolicy: Make MPOL_LOCAL a real policy

From: Peter Zijlstra Make MPOL_LOCAL a real and exposed policy such that applications that relied on the previous default behaviour can explicitly request it. Requested-by: Christoph Lameter Reviewed-by: Rik van Riel Cc: Lee Schermerhorn Cc: Andrew Morton Cc: Linus Torvalds Signed-off-by: P

[PATCH 17/40] mm: mempolicy: Add MPOL_MF_NOOP

From: Lee Schermerhorn NOTE: I have not yet addressed by own review feedback of this patch. At this point I'm trying to construct a baseline tree and will apply my own review feedback later and then fold it in. This patch augments the MPOL_MF_LAZY feature by adding a "NOOP" polic

[PATCH 15/40] mm: numa: Create basic numa page hinting infrastructure

Note: This patch started as "mm/mpol: Create special PROT_NONE infrastructure" and preserves the basic idea but steals *very* heavily from "autonuma: numa hinting page faults entry points" for the actual fault handlers without the migration parts. The end result is

[PATCH 18/40] mm: mempolicy: Check for misplaced page

From: Lee Schermerhorn This patch provides a new function to test whether a page resides on a node that is appropriate for the mempolicy for the vma and address where the page is supposed to be mapped. This involves looking up the node where the page belongs. So, the function returns that node

[PATCH 19/40] mm: migrate: Introduce migrate_misplaced_page()

From: Peter Zijlstra Note: This was originally based on Peter's patch "mm/migrate: Introduce migrate_misplaced_page()" but borrows extremely heavily from Andrea's "autonuma: memory follows CPU algorithm and task/mm_autonuma stats collection". The end result is barely recog

[PATCH 31/40] mm: numa: Structures for Migrate On Fault per NUMA migration rate limiting

From: Andrea Arcangeli This defines the per-node data used by Migrate On Fault in order to rate limit the migration. The rate limiting is applied independently to each destination node. Signed-off-by: Andrea Arcangeli Signed-off-by: Mel Gorman --- include/linux/mmzone.h | 13 +

Re: [PATCH 2/7] gpio/em: convert to linear IRQ domain

On Wed, Nov 21, 2012 at 3:58 PM, Grant Likely wrote: > On Tue, 16 Oct 2012 21:22:20 +0200, Linus Walleij > wrote: >> The code in the em driver seems to want to try to do the job of >> the linear IRQ domain (allocate descriptors and grab a virtual >> range). So why not just use the linear IRQ dom

[PATCH 29/40] mm: numa: Migrate on reference policy

This is the simplest possible policy that still does something of note. When a pte_numa is faulted, it is moved immediately. Any replacement policy must at least do better than this and in all likelihood this policy regresses normal workloads. Signed-off-by: Mel Gorman Acked-by: Rik van Riel ---

Re: Device tree node to major/minor?

On Wed, Nov 21, 2012 at 8:48 PM, Simon Glass wrote: > Hi Grant, > > On Wed, Nov 21, 2012 at 7:47 AM, Grant Likely > wrote: >> On Tue, 20 Nov 2012 15:48:24 -0800, Simon Glass wrote: >>> Hi Grant, >>> >>> On Tue, Nov 20, 2012 at 2:32 PM, Grant Likely >>> wrote: >>> > On Tue, Nov 20, 2012 at 10:

[PATCH 28/40] mm: numa: Add pte updates, hinting and migration stats

It is tricky to quantify the basic cost of automatic NUMA placement in a meaningful manner. This patch adds some vmstats that can be used as part of a basic costing model. u= basic unit = sizeof(void *) Ca = cost of struct page access = sizeof(struct page) / u Cpte = Cost PTE access = Ca Cup

[PATCH 1/2] mmc: dw_mmc: exynos: Stop claiming wp-gpio

The exynos code claimed wp-gpio with devm_gpio_request() but never did anything with it. That meant that anyone using a write protect GPIO would effectively be write protected all the time. A future change will move the wp-gpio support to the core dw_mmc.c file. Now the exynos-specific code won'

[PATCH 02/10] ASoC: wm8753: remove invalid free of devm_ allocated data

Fixes following warning. sound/soc/codecs/wm8753.c:1594:1-6: WARNING: invalid free of devm_ allocated data Signed-off-by: Tushar Behera --- sound/soc/codecs/wm8753.c |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/sound/soc/codecs/wm8753.c b/sound/soc/codecs/wm8753.c in

[PATCH 27/40] mm: sched: numa: Implement slow start for working set sampling

From: Peter Zijlstra Add a 1 second delay before starting to scan the working set of a task and starting to balance it amongst nodes. [ note that before the constant per task WSS sampling rate patch the initial scan would happen much later still, in effect that patch caused this regression.

[PATCH 26/40] sched, numa, mm: Count WS scanning against present PTEs, not virtual memory ranges

By accounting against the present PTEs, scanning speed reflects the actual present (mapped) memory. Suggested-by: Ingo Molnar Signed-off-by: Peter Zijlstra Cc: Linus Torvalds Cc: Andrew Morton Cc: Peter Zijlstra Cc: Andrea Arcangeli Cc: Rik van Riel Cc: Mel Gorman Signed-off-by: Ingo Molna

[PATCH 2/4] video: vt8500: Fix invalid free of devm_ allocated data

While at it, also fix the related return statements. Signed-off-by: Tushar Behera --- drivers/video/vt8500lcdfb.c | 15 +++ 1 files changed, 3 insertions(+), 12 deletions(-) diff --git a/drivers/video/vt8500lcdfb.c b/drivers/video/vt8500lcdfb.c index 5777adc..2438368 100644 --- a/

[PATCH 25/40] mm: sched: numa: Implement constant, per task Working Set Sampling (WSS) rate

From: Peter Zijlstra Previously, to probe the working set of a task, we'd use a very simple and crude method: mark all of its address space PROT_NONE. That method has various (obvious) disadvantages: - it samples the working set at dissimilar rates, giving some tasks a sampling quality adva

[PATCH 24/40] mm: numa: Add fault driven placement and migration

From: Peter Zijlstra NOTE: This patch is based on "sched, numa, mm: Add fault driven placement and migration policy" but as it throws away all the policy to just leave a basic foundation I had to drop the signed-offs-by. This patch creates a bare-bones method for setting PTEs pte

[PATCH 22/40] mm: mempolicy: Implement change_prot_numa() in terms of change_protection()

From: Lee Schermerhorn This patch converts change_prot_numa() to use change_protection(). As pte_numa and friends check the PTE bits directly it is necessary for change_protection() to use pmd_mknuma(). Hence the required modifications to change_protection() are a little clumsy but the end result

[PATCH 23/40] mm: mempolicy: Hide MPOL_NOOP and MPOL_MF_LAZY from userspace for now

The use of MPOL_NOOP and MPOL_MF_LAZY to allow an application to explicitly request lazy migration is a good idea but the actual API has not been well reviewed and once released we have to support it. For now this patch prevents an application using the services. This will need to be revisited. Si

[PATCH 21/40] mm: mempolicy: Add MPOL_MF_LAZY

From: Lee Schermerhorn NOTE: Once again there is a lot of patch stealing and the end result is sufficiently different that I had to drop the signed-offs. Will re-add if the original authors are ok with that. This patch adds another mbind() flag to request "lazy migration". The f

[PATCH 20/40] mm: mempolicy: Use _PAGE_NUMA to migrate pages

Note: Based on "mm/mpol: Use special PROT_NONE to migrate pages" but sufficiently different that the signed-off-bys were dropped Combine our previous _PAGE_NUMA, mpol_misplaced and migrate_misplaced_page() pieces into an effective migrate on fault scheme. Note that (on x86) we rely on PRO

[PATCH 14/40] mm: numa: split_huge_page: transfer the NUMA type from the pmd to the pte

From: Andrea Arcangeli When we split a transparent hugepage, transfer the NUMA type from the pmd to the pte if needed. Signed-off-by: Andrea Arcangeli Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel --- mm/huge_memory.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/mm/huge_mem

[PATCH 13/40] mm: numa: Support NUMA hinting page faults from gup/gup_fast

From: Andrea Arcangeli Introduce FOLL_NUMA to tell follow_page to check pte/pmd_numa. get_user_pages must use FOLL_NUMA, and it's safe to do so because it always invokes handle_mm_fault and retries the follow_page later. KVM secondary MMU page faults will trigger the NUMA hinting page faults thr

[PATCH 12/40] mm: numa: pte_numa() and pmd_numa()

From: Andrea Arcangeli Implement pte_numa and pmd_numa. We must atomically set the numa bit and clear the present bit to define a pte_numa or pmd_numa. Once a pte or pmd has been set as pte_numa or pmd_numa, the next time a thread touches a virtual address in the corresponding virtual range, a

[PATCH 11/40] mm: numa: define _PAGE_NUMA

From: Andrea Arcangeli The objective of _PAGE_NUMA is to be able to trigger NUMA hinting page faults to identify the per NUMA node working set of the thread at runtime. Arming the NUMA hinting page fault mechanism works similarly to setting up a mprotect(PROT_NONE) virtual range: the present bit

[PATCH 08/40] mm: compaction: Move migration fail/success stats to migrate.c

The compact_pages_moved and compact_pagemigrate_failed events are convenient for determining if compaction is active and to what degree migration is succeeding but it's at the wrong level. Other users of migration may also want to know if migration is working properly and this will be particularly

Re: [PATCH v3 11/12] x86, boot: add fields to support load bzImage and ramdisk high

On Thu, Nov 22, 2012 at 12:20 PM, H. Peter Anvin wrote: > On 11/22/2012 12:18 PM, Yinghai Lu wrote: >> >> >> for kexec bzImage --real-mode-entry, code after setup_header will be >> executed. >> > > For real mode entry we go through the real mode path which takes care of > this. What matters is th

[PATCH] watchdog: da9052: Fix invalid free of devm_ allocated data

It is not required to free devm_ allocated data. Since kref_put needs a valid release function, da9052_wdt_release_resources() is not deleted. Fixes following warning. drivers/watchdog/da9052_wdt.c:59:1-6: WARNING: invalid free of devm_ allocated data Signed-off-by: Tushar Behera --- drivers/wa

<    1   2   3   4   5   6   7   8   9   10   >